Triple
T22708542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The String Cheese Incident |
E561527
|
entity |
| Predicate | touringFocus |
P56890
|
FINISHED |
| Object | extensive live touring |
—
|
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: extensive live touring | Statement: [The String Cheese Incident, touringFocus, extensive live touring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touringFocus Context triple: [The String Cheese Incident, touringFocus, extensive live touring]
-
A.
touringScope
chosen
Indicates the extent or range of locations, venues, or areas covered by an entity’s tour or touring activity.
-
B.
touringStyle
Indicates the manner or approach in which an entity conducts or experiences a tour (e.g., type, format, or style of touring).
-
C.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
D.
touringActivity
Indicates an activity where an entity travels from place to place, typically for visiting, performing, or sightseeing purposes.
-
E.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178d11d4081909981872698b6c45e |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:17 p.m.