Triple
T28598431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coquitlam Adanacs |
E723839
|
entity |
| Predicate | provinceLeague |
P12325
|
FINISHED |
| Object | British Columbia |
—
|
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: British Columbia | Statement: [Coquitlam Adanacs, provinceLeague, British Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceLeague Context triple: [Coquitlam Adanacs, provinceLeague, British Columbia]
-
A.
stateLeague
chosen
Indicates that a sports team or club competes in, or is affiliated with, a particular state-level league or competition.
-
B.
countryLeagueScope
Indicates that a league’s scope or coverage is defined at the level of a specific country.
-
C.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
D.
regionLeague
Indicates a relationship where a specific region is associated with, belongs to, or is governed by a particular league or league-level organization.
-
E.
cityLeague
Indicates that a city is associated with, belongs to, or participates in a particular league or organized grouping of cities.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 28, 2026, 4:23 a.m.