Triple
T30418038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rising Tour |
E773812
|
entity |
| Predicate | precededTour |
P114858
|
FINISHED |
| Object | Vote for Change 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: Vote for Change Tour | Statement: [The Rising Tour, precededTour, Vote for Change Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededTour Context triple: [The Rising Tour, precededTour, Vote for Change Tour]
-
A.
previousTour
chosen
Indicates that one entity represents a tour that occurred before another tour in a sequence or timeline.
-
B.
precededByTourArtist
Indicates that one tour artist chronologically comes before another tour artist in a sequence or lineup.
-
C.
precedesInPilgrimage
Indicates that one entity undertakes or occurs in the pilgrimage before another entity in an ordered sequence.
-
D.
precededOnPilgrimageBy
Indicates that one entity went on a pilgrimage earlier in time than another, such that the first entity’s pilgrimage occurred before the second’s.
-
E.
followsTour
Indicates that one entity attends or participates in a tour that occurs after, or as a consequence of, another specified event or tour.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 8:05 p.m.