Triple
T5227064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panama Hattie |
E118015
|
entity |
| Predicate | theatricalRunType |
P54466
|
FINISHED |
| Object | commercial Broadway run |
—
|
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: commercial Broadway run | Statement: [Panama Hattie, theatricalRunType, commercial Broadway run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatricalRunType Context triple: [Panama Hattie, theatricalRunType, commercial Broadway run]
-
A.
theatricalRun
Indicates that a film, play, or performance is being publicly shown in theaters over a defined period of time.
-
B.
broadwayRunType
chosen
Indicates the nature or category of a production’s run on Broadway (for example, original run, revival, limited engagement, or tour transfer).
-
C.
theaterType
Indicates the specific kind or category of theater associated with an entity (e.g., cinema, opera house, drama theater).
-
D.
theatreType
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
E.
theatricalFunction
Indicates the role or purpose something serves within a theatrical context, such as its function in staging, performance, or dramatic presentation.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7addbdb88190baf9f47fc4cbb7fc |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.