Triple
T2366092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muskegon Lumberjacks (hockey) |
E47382
|
entity |
| Predicate | juniorAgeRange |
P2736
|
FINISHED |
| Object | 16–20 |
—
|
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: 16–20 | Statement: [Muskegon Lumberjacks (hockey), juniorAgeRange, 16–20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: juniorAgeRange Context triple: [Muskegon Lumberjacks (hockey), juniorAgeRange, 16–20]
-
A.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
juniorEventsIncluded
Indicates that events involving junior participants or categories are included within a given set, schedule, or scope.
-
C.
juniorDivisionDuration
Indicates the length of time that a junior division or lower-level category remains in effect or is scheduled to run.
-
D.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
E.
youthYears
Indicates the period of time during which an individual spent their youth, typically associated with early development or formative years, often in relation to an organization, activity, or place.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc749f8e0819094144b9dd9db8790 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.