Triple
T529525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lonely Room |
E10993
|
entity |
| Predicate | firstPerformanceWork |
P15234
|
FINISHED |
| Object | original Broadway production of Oklahoma! |
—
|
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: original Broadway production of Oklahoma! | Statement: [Lonely Room, firstPerformanceWork, original Broadway production of Oklahoma!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceWork Context triple: [Lonely Room, firstPerformanceWork, original Broadway production of Oklahoma!]
-
A.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
-
B.
firstPerformanceOpera
Indicates the relationship in which an opera work is presented in its first-ever performance.
-
C.
firstPerformanceContext
Indicates the situational or environmental context in which an entity’s first performance or debut took place.
-
D.
firstExhibited
Indicates the event or context in which something was publicly displayed or presented for the first time.
-
E.
firstPerformanceCountry
Indicates the country in which something (such as a work, show, or performance) was first performed.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d4984c8190ac372171b16bb5e4 |
completed | Feb. 28, 2026, 1:47 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f0dcff1881909c18e8c599c150a1 |
completed | Feb. 28, 2026, 1:42 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.