Triple
T33959859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace Theatre (Columbus, Ohio) |
E870679
|
entity |
| Predicate | hasOrchestraLevelSeating |
P196837
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Palace Theatre (Columbus, Ohio), hasOrchestraLevelSeating, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrchestraLevelSeating Context triple: [Palace Theatre (Columbus, Ohio), hasOrchestraLevelSeating, yes]
-
A.
hasBandSeating
Indicates that a venue or location provides designated seating specifically for a band or musical ensemble.
-
B.
hasBoxSeating
Indicates that an entity provides or includes box seating as a type of seating arrangement.
-
C.
hasBleacherSeating
Indicates that a venue or location is equipped with bleacher-style seating for spectators.
-
D.
hasPrioritySeating
Indicates that one entity provides or designates reserved or preferential seating for another entity.
-
E.
hasSeatingClassification
Indicates that an entity is assigned a specific type or category of seating arrangement or capacity.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
| PDg | Predicate description generation | batch_69fe6b7a823881909dc2037fe25bea24 |
completed | May 8, 2026, 11:02 p.m. |
Created at: May 1, 2026, 1:49 a.m.