Triple
T14157181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duna Arena |
E350842
|
entity |
| Predicate | hasExpandedCapacityForEvents |
P79202
|
FINISHED |
| Object | approximately 12000 |
—
|
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 12000 | Statement: [Duna Arena, hasExpandedCapacityForEvents, approximately 12000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpandedCapacityForEvents Context triple: [Duna Arena, hasExpandedCapacityForEvents, approximately 12000]
-
A.
hasCapacityTo
Indicates that one entity possesses the ability, power, or potential to perform an action or bring about a particular effect in relation to another entity or context.
-
B.
hasEventSpace
Indicates that an entity provides or includes a designated space intended for hosting events.
-
C.
expandedCapacity
Indicates that an entity’s capacity has been increased beyond its previous or standard level.
-
D.
capacityDuringEvent
chosen
Indicates the maximum number of occupants or usage level that a place, system, or resource can handle specifically during a given event.
-
E.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61377de48190a3470d28f0edd34a |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:58 a.m.