Triple
T20809614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Ontario Junior Hockey League |
E512261
|
entity |
| Predicate | ageRangeFocus |
P29430
|
FINISHED |
| Object | late teens to early twenties |
—
|
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: late teens to early twenties | Statement: [Northern Ontario Junior Hockey League, ageRangeFocus, late teens to early twenties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRangeFocus Context triple: [Northern Ontario Junior Hockey League, ageRangeFocus, late teens to early twenties]
-
A.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
hasAgeFocus
chosen
Indicates a relationship where something is characterized or distinguished by a particular age group or age-related emphasis.
-
C.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
-
D.
ageRangeUpper
Indicates the maximum age limit that bounds the upper end of an age range associated with an entity or relationship.
-
E.
ageGroupInvolved
Indicates that a particular age group participates in, is affected by, or is otherwise involved in the specified event or relationship.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d199888190b8b190c928f510b7 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.