Triple
T30757807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The River Tour |
E783137
|
entity |
| Predicate | predecessorTour |
P114858
|
FINISHED |
| Object | Darkness Tour |
—
|
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: Darkness Tour | Statement: [The River Tour, predecessorTour, Darkness Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorTour Context triple: [The River Tour, predecessorTour, Darkness Tour]
-
A.
previousTour
chosen
Indicates that one entity represents a tour that occurred before another tour in a sequence or timeline.
-
B.
predecessorRiding
Indicates that one entity is riding or mounted on another entity that is its predecessor in some defined sequence or ordering.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
predecessorSeries
Indicates that one series directly precedes another in an ordered sequence or lineage.
-
E.
predecessorInExploration
Indicates that one entity explored or investigated something earlier in time than another, establishing a prior step in an exploration sequence.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:39 p.m.