Triple
T36476590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coachella Valley Firebirds |
E898682
|
entity |
| Predicate | homeCapacityIceHockey |
P156462
|
FINISHED |
| Object | approximately 10,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: approximately 10,000 | Statement: [Coachella Valley Firebirds, homeCapacityIceHockey, approximately 10,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCapacityIceHockey Context triple: [Coachella Valley Firebirds, homeCapacityIceHockey, approximately 10,000]
-
A.
iceHockeyArenaCapacity
chosen
Indicates the seating capacity or maximum number of spectators that an ice hockey arena can accommodate.
-
B.
hasIceHockeyCapacity
Indicates that an entity is capable of hosting or accommodating ice hockey activities, such as games or practices.
-
C.
mainIceHockeyVenue
Indicates that a location serves as the primary venue where a team or organization regularly plays its ice hockey games.
-
D.
hasIceRinkDimensions
Indicates that an entity possesses or is characterized by specific ice rink measurements or size specifications.
-
E.
homeArenaHockey
Indicates that a particular arena serves as the designated home venue for a specific hockey team.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.