Triple
T34836535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großer Musikvereinssaal |
E1004214
|
entity |
| Predicate | seatingCapacityStallsAndGallery |
P2491
|
FINISHED |
| Object | about 1744 |
—
|
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: about 1744 | Statement: [Großer Musikvereinssaal, seatingCapacityStallsAndGallery, about 1744]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityStallsAndGallery Context triple: [Großer Musikvereinssaal, seatingCapacityStallsAndGallery, about 1744]
-
A.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
B.
standingCapacity
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
-
C.
hasSeatingCapacityWithStanding
Indicates that an entity has a total seating capacity that explicitly includes standing room capacity as part of its overall accommodation.
-
D.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
E.
mainHallCapacity
Indicates the maximum number of people that the main hall can accommodate at one time.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.