Triple
T37563947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Good Doctor |
E933900
|
entity |
| Predicate | originalProductionTheatreDistrict |
P84874
|
FINISHED |
| Object | Broadway theatre district |
E746
|
NE 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 theatre district | Statement: [The Good Doctor, originalProductionTheatreDistrict, Broadway theatre district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalProductionTheatreDistrict Context triple: [The Good Doctor, originalProductionTheatreDistrict, Broadway theatre district]
-
A.
originalBroadwayProductionTheatre
Indicates the theatre venue where a work’s original Broadway production was staged.
-
B.
basedOnTheatreProductionLocation
Indicates that something is derived from, adapted from, or otherwise grounded in a theatre production that took place at a specific location.
-
C.
originalTheatreOfPremiere
Indicates the theatre where a work was first premiered or originally performed.
-
D.
firstBroadwayProductionTheatre
Indicates the theatre where an entity’s first Broadway production was staged.
-
E.
theaterDistrict
chosen
Indicates that a location is situated within or associated with a designated theater district.
- F. None of above.
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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409f1848788190aafc58fb707829b7 |
completed | June 28, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.