Triple
T35698845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagles |
E1031519
|
entity |
| Predicate | juniorLeagueTier |
P105938
|
FINISHED |
| Object | CHL |
—
|
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: CHL | Statement: [Eagles, juniorLeagueTier, CHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: juniorLeagueTier Context triple: [Eagles, juniorLeagueTier, CHL]
-
A.
juniorTierClassification
Indicates that one entity is assigned a lower or subordinate level within a hierarchical tier structure relative to others.
-
B.
youthTier
chosen
Indicates a classification relationship where an entity is assigned to a specific youth-related level, category, or bracket within a tiered system.
-
C.
developmentLeagueFor
Indicates that one entity serves as a developmental or minor league affiliate for another, typically higher-level, sports team or organization.
-
D.
levelInCJHL
Indicates that an entity participates in or is associated with a specific competitive level within the CJHL (Canadian Junior Hockey League) hierarchy.
-
E.
associatedLeagueLevel
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.