Triple
T22232234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U2 Go Home: Live from Slane Castle |
E549494
|
entity |
| Predicate | setDuringTourLeg |
P146173
|
FINISHED |
| Object | Elevation Tour European leg |
—
|
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: Elevation Tour European leg | Statement: [U2 Go Home: Live from Slane Castle, setDuringTourLeg, Elevation Tour European leg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setDuringTourLeg Context triple: [U2 Go Home: Live from Slane Castle, setDuringTourLeg, Elevation Tour European leg]
-
A.
hasTourLeg
Indicates that a specific segment or leg is part of, or associated with, a larger tour or journey.
-
B.
distancePerLeg
Indicates the distance covered in a single leg or segment of a multi-part journey or route.
-
C.
usedOnTour
chosen
Indicates that something (such as an item, equipment, or resource) is utilized during a tour or touring activity.
-
D.
subsequentLegStart
Indicates that one travel leg or segment begins immediately after the end of another leg in a sequence.
-
E.
trailStopOn
Indicates that one entity stops or terminates at the endpoint of a trail or path associated with another entity.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf3de648190986a734f19643a8c |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.