Triple
T21709867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toftir |
E535872
|
entity |
| Predicate | hasStadiumCapacityApprox |
P13599
|
FINISHED |
| Object | 6000 at Svangaskarð |
—
|
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: 6000 at Svangaskarð | Statement: [Toftir, hasStadiumCapacityApprox, 6000 at Svangaskarð]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStadiumCapacityApprox Context triple: [Toftir, hasStadiumCapacityApprox, 6000 at Svangaskarð]
-
A.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a stadium can accommodate.
-
B.
cityStadiumCapacity
Indicates the maximum number of spectators that a given city’s stadium can accommodate.
-
C.
formerStadiumCapacityApprox
Indicates that an entity’s past stadium capacity is approximately equal to the given number, rather than an exact figure.
-
D.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
E.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5321d34819091f3cd03f7b407c0 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.