Triple
T22588478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goffertstadion |
E564866
|
entity |
| Predicate | hasCapacityRange |
P35147
|
FINISHED |
| Object | 10000-15000 |
—
|
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: 10000-15000 | Statement: [Goffertstadion, hasCapacityRange, 10000-15000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapacityRange Context triple: [Goffertstadion, hasCapacityRange, 10000-15000]
-
A.
hasCapacityType
Indicates that an entity possesses a specific kind or classification of capacity or capability.
-
B.
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.
-
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.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
offersCapacityRange
chosen
Indicates that an entity provides or makes available a service, product, or resource whose capacity is specified as a range between a minimum and maximum value.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615ea5bc8190b7760cd0de9669dd |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:47 p.m.