Triple
T18868017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MHL-B |
E461490
|
entity |
| Predicate | organisedWithinSystem |
P66605
|
FINISHED |
| Object | Russian junior ice hockey system |
—
|
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: Russian junior ice hockey system | Statement: [MHL-B, organisedWithinSystem, Russian junior ice hockey system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organisedWithinSystem Context triple: [MHL-B, organisedWithinSystem, Russian junior ice hockey system]
-
A.
organisedIn
Indicates that an event, activity, or entity is arranged, coordinated, or held within a particular place, context, or organizational framework.
-
B.
organisedWith
Indicates that two or more entities are arranged, coordinated, or structured together as part of the same organizing context or effort.
-
C.
organisedFor
Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
-
D.
tookPlaceInSystem
Indicates that an event or process occurred within, or was hosted by, a particular system or environment.
-
E.
locatedInOrganizationally
chosen
Indicates that one entity is organizationally situated within, or belongs to, another entity in terms of administrative or structural hierarchy.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a6d1d081909b6dab2a5166a317 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.