Triple
T7878551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Division |
E182918
|
entity |
| Predicate | levelInLeagueHierarchy |
P50168
|
FINISHED |
| Object | division |
—
|
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: division | Statement: [Canadian Division, levelInLeagueHierarchy, division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelInLeagueHierarchy Context triple: [Canadian Division, levelInLeagueHierarchy, division]
-
A.
levelInNationalTeamStructure
Indicates the hierarchical tier or rank that an entity occupies within a national team’s organizational structure.
-
B.
competitionHierarchyLevel
Indicates the relative rank or tier of a competition within an overall competitive structure or hierarchy.
-
C.
associatedLeagueLevel
chosen
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
-
D.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
E.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39bd64e481909f699e7dd2818b8f |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:57 p.m.