Triple
T23524688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisville Slugger Field |
E574599
|
entity |
| Predicate | soccerCapacity |
P13599
|
FINISHED |
| Object | about 13,000 |
—
|
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 13,000 | Statement: [Louisville Slugger Field, soccerCapacity, about 13,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soccerCapacity Context triple: [Louisville Slugger Field, soccerCapacity, about 13,000]
-
A.
capacityForWorldCup
Indicates the maximum number of spectators a venue can accommodate specifically for World Cup events.
-
B.
cityStadiumCapacity
Indicates the maximum number of spectators that a given city’s stadium can accommodate.
-
C.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a stadium can accommodate.
-
D.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
E.
playerCapacity
Indicates the maximum number of players that can simultaneously participate in or be accommodated by something (such as a game, session, or venue).
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1ac72bfb88190b7da3837e66e851c |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.