Triple
T10465621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Fidelity |
E246785
|
entity |
| Predicate | broadwayCommercialOutcome |
P94186
|
FINISHED |
| Object | short 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: short run | Statement: [High Fidelity, broadwayCommercialOutcome, short run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadwayCommercialOutcome Context triple: [High Fidelity, broadwayCommercialOutcome, short run]
-
A.
hasBroadwayOpeningContext
Indicates that an entity is associated with contextual details specifically about its Broadway opening (such as time, place, or circumstances of the premiere).
-
B.
hasBroadwayProduction
Indicates that a work or show has been produced and staged in a Broadway theater.
-
C.
broadwayRunType
Indicates the nature or category of a production’s run on Broadway (for example, original run, revival, limited engagement, or tour transfer).
-
D.
broadwayRunEnd
Indicates the date or point in time when a production’s run on Broadway concludes.
-
E.
recordStatusBroadway
Indicates that an entity’s record reflects its status specifically within the context of Broadway-related activities or classifications.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5092d6d408190b6bda4d7ced4601e |
completed | April 7, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:19 p.m.