Triple
T7462619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modo Hockey |
E176287
|
entity |
| Predicate | youthProgram |
P6626
|
FINISHED |
| Object | Modo Hockey junior teams |
—
|
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: Modo Hockey junior teams | Statement: [Modo Hockey, youthProgram, Modo Hockey junior teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: youthProgram Context triple: [Modo Hockey, youthProgram, Modo Hockey junior teams]
-
A.
hasYouthProgram
chosen
Indicates that an entity offers or is associated with an organized program or set of activities specifically designed for young people.
-
B.
youthWing
Indicates that one organization serves as the youth or junior wing of another organization, typically representing younger members aligned with the parent body.
-
C.
youthLeader
Indicates that an entity holds a leadership role within a youth-focused group, organization, or activity.
-
D.
hasVolunteerProgram
Indicates that an organization or entity offers an organized program through which individuals can volunteer their time or services.
-
E.
inspiredPrograms
Indicates that one entity served as a source of inspiration or influence for the creation or design of another entity’s programs.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d80ae08190ba383066cf0cb2ce |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:39 p.m.