Triple
T20436944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadway touring circuit |
E501271
|
entity |
| Predicate | typicalShow |
P5973
|
FINISHED |
| Object | touring Broadway musical |
—
|
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: touring Broadway musical | Statement: [Broadway touring circuit, typicalShow, touring Broadway musical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalShow Context triple: [Broadway touring circuit, typicalShow, touring Broadway musical]
-
A.
typicalShowElements
Indicates that certain elements are characteristically or commonly present in a particular show or type of show.
-
B.
televisionShow
Indicates that one entity is a television show associated with, or featured in relation to, another entity.
-
C.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
D.
typicalVariety
chosen
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
-
E.
typicalCast
Indicates that the associated entities form the usual or characteristic cast of characters commonly appearing in a given work or type of work.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685ef5fc8819089e3f97a63a52f86 |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.