Triple
T8153945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tim Lake |
E190396
|
entity |
| Predicate | usesTimeTravelFor |
P80849
|
FINISHED |
| Object | romantic relationships |
—
|
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: romantic relationships | Statement: [Tim Lake, usesTimeTravelFor, romantic relationships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTimeTravelFor Context triple: [Tim Lake, usesTimeTravelFor, romantic relationships]
-
A.
timeTravelMethod
Indicates the specific mechanism or technique by which an entity performs or experiences time travel.
-
B.
timeTravelDeviceUsed
Indicates that an entity makes use of a device or mechanism that enables travel through time.
-
C.
timeTravelTo
Indicates traveling from one point in time to another, typically different, point in time.
-
D.
timeTravelElement
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.
-
E.
timeTravelDirection
Indicates the temporal direction in which time travel occurs, such as moving into the past or into the future.
- F. None of above. chosen
Provenance (4 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d566b08190a6bb672f9c368806 |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39ba412881908a053e88f29a9588 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:37 p.m.