Triple
T12805008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LR Vicenza |
E306121
|
entity |
| Predicate | traditionalHomeStadiumCapacityApprox |
P13599
|
FINISHED |
| Object | 12000–13000 |
—
|
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: 12000–13000 | Statement: [LR Vicenza, traditionalHomeStadiumCapacityApprox, 12000–13000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHomeStadiumCapacityApprox Context triple: [LR Vicenza, traditionalHomeStadiumCapacityApprox, 12000–13000]
-
A.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
B.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a 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.
homeBallparkCapacityApprox
Indicates that the relationship specifies an approximate seating capacity of a team's home ballpark.
-
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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7f370c8190b3fc39c1b63394c6 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.