Triple
T13231368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadhurst Theatre |
E315025
|
entity |
| Predicate | isProsceniumStage |
P91318
|
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: [Broadhurst Theatre, isProsceniumStage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProsceniumStage Context triple: [Broadhurst Theatre, isProsceniumStage, true]
-
A.
isMainStageOf
Indicates that one entity serves as the primary or central stage or platform on which the other entity occurs, is presented, or is featured.
-
B.
usesStageType
chosen
Indicates that one entity employs or operates with a particular type or category of stage.
-
C.
hasStagePlayCounterpart
Indicates that one work has a corresponding or equivalent version in the form of a stage play.
-
D.
usesStage
Indicates that one entity employs or operates on another entity at a particular phase or stage within a process or workflow.
-
E.
stageTechnology
Indicates that a particular technology is used, implemented, or deployed at a specific stage or phase within a process, workflow, or lifecycle.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d34ff288190bdb550a019b7a470 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:22 p.m.