Triple
T27639343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Do Not Belong Together |
E696547
|
entity |
| Predicate | firstProductionVenue |
P58338
|
FINISHED |
| Object | Off-Broadway |
—
|
NE NERFINISHED |
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: Off-Broadway | Statement: [We Do Not Belong Together, firstProductionVenue, Off-Broadway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstProductionVenue Context triple: [We Do Not Belong Together, firstProductionVenue, Off-Broadway]
-
A.
debutVenue
Indicates the venue or location where an entity (such as a person, group, or work) made its first public appearance or performance.
-
B.
firstODIVenue
Indicates that the subject is the venue where an ODI (One Day International) cricket match was first held or hosted.
-
C.
firstPerformanceProduction
Indicates that a production is the one in which a work (e.g., a play, musical, or performance piece) was first publicly performed.
-
D.
firstPerformanceAt
chosen
Indicates the location or event at which an entity (such as a work or performance) was first performed.
-
E.
firstPerformanceLocationOfWorkAppearingIn
Indicates the location where a work was first performed or premiered.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: April 27, 2026, 2:25 p.m.