Triple
T36480120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Andrews |
E898788
|
entity |
| Predicate | timeTravelInvolvedInStory |
P129055
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Charlie Andrews, timeTravelInvolvedInStory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeTravelInvolvedInStory Context triple: [Charlie Andrews, timeTravelInvolvedInStory, yes]
-
A.
timeTravelInvolvement
chosen
Indicates that an entity participates in, is affected by, or is otherwise involved in an instance of time travel.
-
B.
timeTravelExperimentDateInStory
Indicates the date on which a time travel experiment occurs within the narrative timeline of the story.
-
C.
timeTravelType
Indicates the specific method or mechanism by which time travel is carried out in a given context.
-
D.
timeTravelTo
Indicates traveling from one point in time to another, typically different, point in time.
-
E.
timeTravelTrigger
Indicates an event, condition, or mechanism that initiates or enables time travel to occur.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.