Triple
T5404677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Checkers |
E120861
|
entity |
| Predicate | playsProfessional |
P63796
|
FINISHED |
| Object | ice hockey |
—
|
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: ice hockey | Statement: [Charlotte Checkers, playsProfessional, ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsProfessional Context triple: [Charlotte Checkers, playsProfessional, ice hockey]
-
A.
playIn
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
-
B.
plays
Indicates that an entity engages in or performs an activity, game, role, or piece of music.
-
C.
playType
Indicates the specific category or style of play or performance associated with an event or action.
-
D.
playedFrom
Indicates that an action of playing (such as media playback or a performance) originated from a particular source or starting point.
-
E.
notablePlayPlayer
Indicates that a player is notably associated with a particular play, such as by making a significant or memorable contribution in it.
- F. None of above. chosen
Provenance (4 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8931302c81908afcb0f011e91f09 |
completed | March 20, 2026, 5:51 p.m. |
Created at: March 20, 2026, 2:05 p.m.