Triple
T28997120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapporo Concert Hall Kitara |
E736196
|
entity |
| Predicate | hasChamberHallCapacity |
P76818
|
FINISHED |
| Object | 453 |
—
|
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: 453 | Statement: [Sapporo Concert Hall Kitara, hasChamberHallCapacity, 453]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChamberHallCapacity Context triple: [Sapporo Concert Hall Kitara, hasChamberHallCapacity, 453]
-
A.
hasSmallHallCapacity
Indicates that the capacity of a hall is below a defined threshold, classifying it as small.
-
B.
hasOrchestraPitCapacity
Indicates the number of people that can be accommodated in the orchestra pit associated with a venue or performance space.
-
C.
hasSecondaryHallCapacity
chosen
Indicates that an entity possesses a specified capacity for a secondary hall or auxiliary event space.
-
D.
hasTertiaryHallCapacity
Indicates that an entity has a specified seating or usage capacity in its tertiary (third-level) hall or auditorium.
-
E.
venueCapacityApproximate
Indicates an approximate or estimated capacity of a venue in terms of how many people it can accommodate.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 28, 2026, 9:32 a.m.