Triple
T4167892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jekyll & Hyde |
E84487
|
entity |
| Predicate | broadwayRunType |
P54466
|
FINISHED |
| Object | Broadway production |
—
|
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: Broadway production | Statement: [Jekyll & Hyde, broadwayRunType, Broadway production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadwayRunType Context triple: [Jekyll & Hyde, broadwayRunType, Broadway production]
-
A.
broadwayRunStatus
Indicates the status of a production’s run on Broadway, such as whether it is upcoming, currently running, or has closed.
-
B.
broadwayRunEnd
Indicates the date or point in time when a production’s run on Broadway concludes.
-
C.
theatricalRun
Indicates that a film, play, or performance is being publicly shown in theaters over a defined period of time.
-
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.
originalBroadwayRunLength
Indicates the duration of time that a production’s initial run on Broadway lasted.
- F. None of above. chosen
Provenance (4 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c573788190a60ab3f83b07a6f6 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af01ee94ec8190aa6dde54d4571c04 |
completed | March 9, 2026, 5:22 p.m. |
Created at: March 9, 2026, 3:44 p.m.