Triple
T25485342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartans |
E638688
|
entity |
| Predicate | homeVenueForSport |
P39293
|
FINISHED |
| Object | Greensboro Coliseum for men's basketball |
—
|
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: Greensboro Coliseum for men's basketball | Statement: [Spartans, homeVenueForSport, Greensboro Coliseum for men's basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueForSport Context triple: [Spartans, homeVenueForSport, Greensboro Coliseum for men's basketball]
-
A.
sportsVenueFor
chosen
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
B.
gameVenue
Indicates the location or facility where a game or match is held.
-
C.
ownsSportsVenue
Indicates that one entity possesses legal ownership or controlling property rights over a sports venue used for athletic or sporting events.
-
D.
Game4Venue
Indicates that a particular game is scheduled to take place at a specific venue.
-
E.
homeVenueTeam1City
Indicates that a specific city serves as the home venue location for the first team in a given context or event.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f77c4cfc819097efb731d25b3452 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:32 p.m.