Triple
T30798893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bent (stage production) |
E784310
|
entity |
| Predicate | notableBroadwayCity |
P207310
|
FINISHED |
| Object | New York City |
E40
|
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: New York City | Statement: [Bent (stage production), notableBroadwayCity, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBroadwayCity Context triple: [Bent (stage production), notableBroadwayCity, New York City]
-
A.
originalBroadwayCity
Indicates the city where a theatrical production first opened on Broadway.
-
B.
notableCityInTheater
Indicates that a city holds particular significance or prominence within a specified theater (such as a military, cultural, or operational region).
-
C.
preBroadwayCity
Indicates the city where a production was staged or developed prior to its official Broadway run.
-
D.
broadwayLocation
Indicates that an entity is located on, near, or associated with Broadway (typically the Broadway theater district or street).
-
E.
notableCityIncluded
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
- F. None of above. chosen
Provenance (5 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28c7b225e0819087bd6dab22c04874 |
completed | June 10, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:42 p.m.