Triple
T32551563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnstown Tomahawks |
E831986
|
entity |
| Predicate | playsJuniorLevel |
P178206
|
FINISHED |
| Object | North American Hockey League |
—
|
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: North American Hockey League | Statement: [Johnstown Tomahawks, playsJuniorLevel, North American Hockey League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsJuniorLevel Context triple: [Johnstown Tomahawks, playsJuniorLevel, North American Hockey League]
-
A.
junior
Indicates that one entity holds a lower rank, status, or level of experience relative to another within a shared context.
-
B.
juniorTierClassification
chosen
Indicates that one entity is assigned a lower or subordinate level within a hierarchical tier structure relative to others.
-
C.
juniorLevelEvent
Indicates that an event is classified as being at a junior or entry level in terms of required experience or seniority.
-
D.
juniorProgram
Indicates that one entity holds a junior or subordinate program position or role in relation to another entity.
-
E.
rookiePlayer
Indicates that the player is in their first season or initial stage of professional participation in the sport or 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:02 a.m.