Triple
T6188183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Coliseum |
E138115
|
entity |
| Predicate | hasHomeTeamSport |
P24656
|
FINISHED |
| Object | professional 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: professional basketball | Statement: [Raleigh Coliseum, hasHomeTeamSport, professional basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeTeamSport Context triple: [Raleigh Coliseum, hasHomeTeamSport, professional basketball]
-
A.
homeTeamSport
chosen
Indicates that a particular sport is the primary or designated sport played by a given home team.
-
B.
hasSportsTeam
Indicates that an entity possesses, sponsors, or is represented by a sports team.
-
C.
containsSportsTeam
Indicates that one entity (typically a location or organization) has a sports team as part of it or within its boundaries.
-
D.
playsHomeGamesOn
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
E.
hasHomeGameSite
Indicates that an entity’s designated location for hosting its home games is another specified entity (the home game site).
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06217be288190997032c8c4839fa5 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.