Triple
T5104269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cats (musical) |
E115051
|
entity |
| Predicate | touringProductions |
P50492
|
FINISHED |
| Object | multiple international 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: multiple international tours | Statement: [Cats (musical), touringProductions, multiple international tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touringProductions Context triple: [Cats (musical), touringProductions, multiple international tours]
-
A.
hasTouringProductions
chosen
Indicates that an entity has one or more touring versions or productions that travel to different locations.
-
B.
featuredInTourSetlistOf
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
C.
touringArtist
Indicates that an artist is currently traveling to perform or exhibit their work in multiple locations.
-
D.
notableTour
Indicates that an entity is recognized for having a significant or well-known tour associated with it.
-
E.
tourSupportFor
Indicates that one entity provides support for another entity’s tour, such as by sponsoring, organizing, or assisting with its execution.
- 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7588c1cc81909d380f91ee214808 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.