Triple
T28302509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cidade das Artes |
E713745
|
entity |
| Predicate | hasSmallAuditoriumCapacity |
P135163
|
FINISHED |
| Object | approximately 450 |
—
|
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: approximately 450 | Statement: [Cidade das Artes, hasSmallAuditoriumCapacity, approximately 450]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSmallAuditoriumCapacity Context triple: [Cidade das Artes, hasSmallAuditoriumCapacity, approximately 450]
-
A.
hasSmallHallCapacity
chosen
Indicates that the capacity of a hall is below a defined threshold, classifying it as small.
-
B.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
C.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
-
D.
typicalSeatingCapacityLowerBound
Indicates the minimum number of seats that an entity is typically designed or expected to provide.
-
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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644b3c6088190b3a20e8916fcddba |
completed | May 2, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:35 p.m.