Triple
T5111470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time-Turner |
E115221
|
entity |
| Predicate | timeTravelDirection |
P61649
|
FINISHED |
| Object | backwards in time |
—
|
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: backwards in time | Statement: [Time-Turner, timeTravelDirection, backwards in time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeTravelDirection Context triple: [Time-Turner, timeTravelDirection, backwards in time]
-
A.
timeTravelTo
Indicates traveling from one point in time to another, typically different, point in time.
-
B.
timeTravelFrom
Indicates a relationship where an entity initiates time travel starting from a specific time or temporal location.
-
C.
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.
-
D.
timeTravelMethod
Indicates the specific mechanism or technique by which an entity performs or experiences time travel.
-
E.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ca57e881908242def2a032902e |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:41 p.m.