Triple
T31347154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace |
E799476
|
entity |
| Predicate | timeTravelStatus |
P51702
|
FINISHED |
| Object | sent back from future |
—
|
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: sent back from future | Statement: [Grace, timeTravelStatus, sent back from future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeTravelStatus Context triple: [Grace, timeTravelStatus, sent back from future]
-
A.
timeTravelTo
Indicates traveling from one point in time to another, typically different, point in time.
-
B.
timeTravelDirection
Indicates the temporal direction in which time travel occurs, such as moving into the past or into the future.
-
C.
timeTravelElement
chosen
Indicates that the situation, event, or narrative involves an element of time travel, such as moving between different points in time or altering temporal sequences.
-
D.
timeTravelType
Indicates the specific method or mechanism by which time travel is carried out in a given context.
-
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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:17 p.m.