Triple
T34905713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kammerspiele |
E1006719
|
entity |
| Predicate | commonSeatingArrangement |
P131527
|
FINISHED |
| Object | flexible seating |
—
|
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: flexible seating | Statement: [Kammerspiele, commonSeatingArrangement, flexible seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSeatingArrangement Context triple: [Kammerspiele, commonSeatingArrangement, flexible seating]
-
A.
seatingConfiguration
Indicates how seats are arranged or organized relative to each other in a given context.
-
B.
hasFlexibleSeating
chosen
Indicates that an entity provides seating arrangements that can be easily rearranged, adjusted, or reconfigured to suit different uses or preferences.
-
C.
typicalSeat
Indicates the usual or standard seating position or location associated with an entity in a given context.
-
D.
seatingDirection
Indicates the orientation or facing direction in which an entity is seated relative to a reference point or object.
-
E.
hasSeatingNearby
Indicates that suitable seating is available in close proximity to the referenced entity or location.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 3, 2026, 4 p.m.