Triple
T28439590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace Theatre, London |
E715668
|
entity |
| Predicate | hasAuditoriumLayout |
P70537
|
FINISHED |
| Object | proscenium arch stage |
—
|
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: proscenium arch stage | Statement: [Palace Theatre, London, hasAuditoriumLayout, proscenium arch stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuditoriumLayout Context triple: [Palace Theatre, London, hasAuditoriumLayout, proscenium arch stage]
-
A.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
-
B.
shapeOfOriginalAuditorium
Indicates the geometric form or layout that characterized the auditorium in its original design or construction.
-
C.
auditoriumType
chosen
Indicates the specific kind or category of auditorium associated with an entity.
-
D.
hasTicketHallDesign
Indicates that an entity possesses or is characterized by a particular design or layout of its ticket hall.
-
E.
hasBoxSeating
Indicates that an entity provides or includes box seating as a type of seating arrangement.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 1:45 a.m.