Triple
T162193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rice Owls |
E3311
|
entity |
| Predicate | footballHomeCapacity |
P3507
|
FINISHED |
| Object | Rice Stadium capacity approximately 47,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: Rice Stadium capacity approximately 47,000 | Statement: [Rice Owls, footballHomeCapacity, Rice Stadium capacity approximately 47,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footballHomeCapacity Context triple: [Rice Owls, footballHomeCapacity, Rice Stadium capacity approximately 47,000]
-
A.
homeStadiumCapacity
chosen
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
B.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
C.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
D.
homeStadiumOf
Indicates that a particular stadium serves as the primary home venue for a specific sports team or organization.
-
E.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2585877648190a2ec320182a69343 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256623704819089d9eeefe05858ce |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.