Triple
T4864129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Producers (2001 Broadway production) |
E108726
|
entity |
| Predicate | broadwayRunEnded |
P25300
|
FINISHED |
| Object | 2007-04-22 |
—
|
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: 2007-04-22 | Statement: [The Producers (2001 Broadway production), broadwayRunEnded, 2007-04-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadwayRunEnded Context triple: [The Producers (2001 Broadway production), broadwayRunEnded, 2007-04-22]
-
A.
broadwayRunEnd
chosen
Indicates the date or point in time when a production’s run on Broadway concludes.
-
B.
broadwayRunStatus
Indicates the status of a production’s run on Broadway, such as whether it is upcoming, currently running, or has closed.
-
C.
BroadwayRunStart
Indicates the date or point in time when a production’s run on Broadway begins.
-
D.
hasBroadwayOpeningContext
Indicates that an entity is associated with contextual details specifically about its Broadway opening (such as time, place, or circumstances of the premiere).
-
E.
broadwayRunType
Indicates the nature or category of a production’s run on Broadway (for example, original run, revival, limited engagement, or tour transfer).
- 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7718e48190af4c0d1abfa87795 |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.