Triple
T12551958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wizard of Oz in Concert: Dreams Come True |
E300117
|
entity |
| Predicate | hasAllStarCast |
P31694
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Wizard of Oz in Concert: Dreams Come True, hasAllStarCast, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllStarCast Context triple: [The Wizard of Oz in Concert: Dreams Come True, hasAllStarCast, true]
-
A.
hasEnsembleCast
chosen
Indicates that a work features an ensemble cast, meaning multiple principal performers share roughly equal prominence rather than having a single clear lead.
-
B.
starredActor
Indicates that an actor performed a leading or significant role in a particular production or work.
-
C.
originalCast
Indicates that the subject is a member of the initial group of performers or participants who first originated a role or production.
-
D.
hasAllStarSelections
Indicates that an entity (typically an athlete) has been chosen to participate in one or more All-Star events or games.
-
E.
hasCrewMember
Indicates that an entity includes or employs another entity as a member of its crew.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:58 p.m.