Triple
T3157098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norris Division |
E66009
|
entity |
| Predicate | playoffRivalry |
P24372
|
FINISHED |
| Object | Chicago Blackhawks vs Detroit Red Wings |
—
|
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: Chicago Blackhawks vs Detroit Red Wings | Statement: [Norris Division, playoffRivalry, Chicago Blackhawks vs Detroit Red Wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffRivalry Context triple: [Norris Division, playoffRivalry, Chicago Blackhawks vs Detroit Red Wings]
-
A.
notableRivalry
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
-
B.
hasRivalrySeries
chosen
Indicates a recurring competitive relationship or series of contests held between two entities.
-
C.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
-
D.
hadRivalryGames
Indicates that there were competitive or rivalrous games or matches played between the entities.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5eafa4c8190a65cc1312823144c |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.