Triple
T14253705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Lock |
E353331
|
entity |
| Predicate | effectOnOutside |
P58916
|
FINISHED |
| Object | external time travelers cannot access sealed region |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: external time travelers cannot access sealed region | Statement: [Time Lock, effectOnOutside, external time travelers cannot access sealed region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnOutside Context triple: [Time Lock, effectOnOutside, external time travelers cannot access sealed region]
-
A.
effectOnOthers
chosen
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
B.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
C.
placeOfEffect
Indicates the location or setting where an action, event, or effect takes place or is realized.
-
D.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
E.
effectOnSystem
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6297f38c819090d7c7fd8bfa2e9e |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:09 a.m.