Triple
T14666501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odessa, Texas |
E344388
|
entity |
| Predicate | RatliffStadiumCapacity |
P103582
|
FINISHED |
| Object | over 19000 spectators |
—
|
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: over 19000 spectators | Statement: [Odessa, Texas, RatliffStadiumCapacity, over 19000 spectators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RatliffStadiumCapacity Context triple: [Odessa, Texas, RatliffStadiumCapacity, over 19000 spectators]
-
A.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
B.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
C.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
D.
ALTeamBallpark
Indicates that an American League baseball team is associated with or plays its home games in a particular ballpark.
-
E.
venueCapacityApproximate
chosen
Indicates an approximate or estimated capacity of a venue in terms of how many people it can accommodate.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54c69f8819080a37161deecfba8 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.