Triple
T28518945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderclap |
E721702
|
entity |
| Predicate | partOfJourneyTo |
P195808
|
FINISHED |
| Object | the Dark Tower |
—
|
NE NERFINISHED |
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: the Dark Tower | Statement: [Thunderclap, partOfJourneyTo, the Dark Tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfJourneyTo Context triple: [Thunderclap, partOfJourneyTo, the Dark Tower]
-
A.
journeyFrom
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
-
B.
occursDuringJourneyTo
Indicates that an event or action takes place while a journey to a specified destination is in progress.
-
C.
withinTravelTo
Indicates that one location is close enough to another that traveling between them is feasible or practical within a specified limit (such as time or distance).
-
D.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
E.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: April 28, 2026, 3:19 a.m.