Triple
T6410265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Arts Centre Orchestra |
E127685
|
entity |
| Predicate | hasTouringScope |
P56890
|
FINISHED |
| Object | national tours |
—
|
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: national tours | Statement: [National Arts Centre Orchestra, hasTouringScope, national tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouringScope Context triple: [National Arts Centre Orchestra, hasTouringScope, national tours]
-
A.
touringScope
chosen
Indicates the extent or range of locations, venues, or areas covered by an entity’s tour or touring activity.
-
B.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
C.
hasTouringReputation
Indicates that an entity is recognized or reputed for its activities, performance, or presence while traveling or touring.
-
D.
hasSubTour
Indicates that one tour, route, or itinerary is contained within or forms a component part of another larger tour.
-
E.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cf81508190bc09e58ec45bc858 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:41 p.m.