Triple
T26805747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadio Arechi |
E671830
|
entity |
| Predicate | hasMaximumCapacity |
P14460
|
FINISHED |
| Object | about 40000 |
—
|
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 40000 | Statement: [Stadio Arechi, hasMaximumCapacity, about 40000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumCapacity Context triple: [Stadio Arechi, hasMaximumCapacity, about 40000]
-
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.
maximumCapacity
chosen
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
C.
hasCapacityProperty
Indicates that an entity is associated with a capacity-related characteristic, such as volume, throughput, or maximum amount it can hold or handle.
-
D.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
-
E.
hasStandingCapacity
Indicates that an entity is capable of maintaining or supporting a specified condition, function, or load on an ongoing basis.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 27, 2026, 4:26 a.m.