Triple
T29628280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Calder Cup playoffs |
E755202
|
entity |
| Predicate | championAffiliation |
P2682
|
FINISHED |
| Object | Columbus Blue Jackets |
—
|
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: Columbus Blue Jackets | Statement: [2016 Calder Cup playoffs, championAffiliation, Columbus Blue Jackets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championAffiliation Context triple: [2016 Calder Cup playoffs, championAffiliation, Columbus Blue Jackets]
-
A.
championConferenceAffiliation
Indicates a relationship where a champion (e.g., a winning team or individual) is associated with the conference or league in which they achieved that championship.
-
B.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
-
C.
championNationality
Indicates the country or nationality that a champion represents or is associated with.
-
D.
championOwner
Indicates that one entity is the owner or holder of a championship title associated with another entity.
-
E.
champion
chosen
Indicates that one entity has won a competition or contest and holds the top position or title over others.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 6:39 p.m.