Triple
T6688346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harpa Concert Hall and Conference Centre |
E152157
|
entity |
| Predicate | mainHallCapacity |
P72212
|
FINISHED |
| Object | 1800 |
—
|
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: 1800 | Statement: [Harpa Concert Hall and Conference Centre, mainHallCapacity, 1800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainHallCapacity Context triple: [Harpa Concert Hall and Conference Centre, mainHallCapacity, 1800]
-
A.
courtyardCapacity
Indicates the maximum number of entities that can be accommodated in a courtyard at the same time.
-
B.
numberOfHalls
Indicates the quantity of halls associated with a given entity or location.
-
C.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
D.
hasMainHall
Indicates that an entity possesses or includes a primary or central hall as a significant internal space.
-
E.
typicalSeatingCapacityUpperBound
Indicates the maximum number of seats that a venue or vehicle is typically designed or allowed to accommodate under normal conditions.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cd0d939081908ede0bb6ce19f559 |
completed | March 27, 2026, 6:31 p.m. |
Created at: March 27, 2026, 2:04 p.m.