Triple
T24021292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legends Tour |
E594827
|
entity |
| Predicate | relatedTour |
P127287
|
FINISHED |
| Object | European 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: European Tour | Statement: [Legends Tour, relatedTour, European Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTour Context triple: [Legends Tour, relatedTour, European Tour]
-
A.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
B.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
C.
tourComponentOf
chosen
Indicates that something functions as a constituent part or segment of a larger tour.
-
D.
relatedExpedition
Indicates that one expedition has a connection or association with another expedition, such as being part of the same project, time period, or thematic context.
-
E.
subjectOfTour
Indicates that an entity serves as the main focus, destination, or theme of a 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5aaf8588190b266557d573504b8 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:47 p.m.