Triple
T31626192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Time Tunnel |
E807030
|
entity |
| Predicate | timeTravelInFiction |
P60994
|
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: [The Time Tunnel, timeTravelInFiction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeTravelInFiction Context triple: [The Time Tunnel, timeTravelInFiction, yes]
-
A.
timeTravelType
Indicates the specific method or mechanism by which time travel is carried out in a given context.
-
B.
fictionalTime
chosen
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
C.
timeTravelInvolvement
Indicates that an entity participates in, is affected by, or is otherwise involved in an instance of time travel.
-
D.
timeTravelPurpose
Indicates that an instance of time travel is undertaken with a specific goal, motive, or intended outcome in mind.
-
E.
timeTravelTo
Indicates traveling from one point in time to another, typically different, point in time.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8e0ebcc8190959911bbf9c977d1 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:43 p.m.