Triple
T794452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tri-City Americans |
E16986
|
entity |
| Predicate | homeCountryLeagueSystem |
P14340
|
FINISHED |
| Object | North American major junior 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: North American major junior hockey | Statement: [Tri-City Americans, homeCountryLeagueSystem, North American major junior hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCountryLeagueSystem Context triple: [Tri-City Americans, homeCountryLeagueSystem, North American major junior hockey]
-
A.
countryOfLeague
Indicates the country in which a given league is based or officially belongs.
-
B.
homeRegionLeague
Indicates that a league is the primary or native regional competition associated with an entity (such as a team or club).
-
C.
countryLeagueSystem
chosen
Indicates that a particular league system operates within, or is associated with, a specific country.
-
D.
homeCountryFA
Indicates that a foreign agent’s primary or originating country is the specified country.
-
E.
homeLeague
Indicates that a sports team primarily competes in, or is officially associated with, a particular league as its main organizational affiliation.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79b976c819085cd381bbd597ca5 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.