Triple
T29221035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaos in Motion Tour |
E740803
|
entity |
| Predicate | tourForBand |
P88801
|
FINISHED |
| Object | Dream Theater |
—
|
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: Dream Theater | Statement: [Chaos in Motion Tour, tourForBand, Dream Theater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourForBand Context triple: [Chaos in Motion Tour, tourForBand, Dream Theater]
-
A.
tourForArtist
chosen
Indicates a relationship where a tour is organized for, associated with, or performed by a specific artist.
-
B.
featuredInTourSetlistOf
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
C.
recordsTour
Indicates that an entity documents or logs information about a tour, such as its details, occurrences, or progress.
-
D.
tourSupportFor
Indicates that one entity provides support for another entity’s tour, such as by sponsoring, organizing, or assisting with its execution.
-
E.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f664329c8c8190abdb1a68f7362c98 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:15 p.m.