Triple
T19536171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bandito Tour |
E488770
|
entity |
| Predicate | tourProductionFeature |
P112025
|
FINISHED |
| Object | elaborate stage design |
—
|
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: elaborate stage design | Statement: [The Bandito Tour, tourProductionFeature, elaborate stage design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourProductionFeature Context triple: [The Bandito Tour, tourProductionFeature, elaborate stage design]
-
A.
tourSupportFor
Indicates that one entity provides support for another entity’s tour, such as by sponsoring, organizing, or assisting with its execution.
-
B.
tourPromotion
Indicates a promotional relationship where an entity is being advertised, marketed, or highlighted as part of a tour or touring event.
-
C.
tourPromoter
Indicates a relationship where an entity organizes, markets, or manages a tour or series of live events for another entity.
-
D.
tourStaple
chosen
Indicates that something is a standard, frequently included element or highlight of a tour.
-
E.
recordsTour
Indicates that an entity documents or logs information about a tour, such as its details, occurrences, or progress.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6386f0fac819081bbc29172c8965e |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.