Triple
T37506820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Illinois Panthers men's basketball |
E932113
|
entity |
| Predicate | homeCourtState |
P47837
|
FINISHED |
| Object | Illinois |
—
|
NE NERFINISHED |
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: Illinois | Statement: [Eastern Illinois Panthers men's basketball, homeCourtState, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCourtState Context triple: [Eastern Illinois Panthers men's basketball, homeCourtState, Illinois]
-
A.
homeCourtOf
Indicates that one location serves as the primary venue or court where a particular team or player regularly hosts its home games or matches.
-
B.
homeCourtDedicatedTo
Indicates that a particular sports venue or court is officially named for or ceremonially assigned in honor of a specific person, group, or entity.
-
C.
homeStateLeagueRegion
Indicates the geographic league region that corresponds to an entity’s home state.
-
D.
homeStateCompetition
Indicates a competitive event or rivalry that takes place within, or is specifically associated with, an entity’s home state.
-
E.
stateOfHomeGround
chosen
Indicates the location or region that serves as an entity’s primary home ground or base of operations.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.