Triple
T3389230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Vortex |
E71376
|
entity |
| Predicate | travelMethod |
P1379
|
FINISHED |
| Object | time corridor |
—
|
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: time corridor | Statement: [Time Vortex, travelMethod, time corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelMethod Context triple: [Time Vortex, travelMethod, time corridor]
-
A.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
C.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
D.
transportFor
Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
-
E.
transportModeIntegration
Indicates that different modes of transportation are coordinated or combined to enable seamless or efficient movement within a journey or transport system.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb666e514819090560d43bfaf55b8 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.