Triple
T17385228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EHT |
E422670
|
entity |
| Predicate | organisesCompetitionFor |
P38960
|
FINISHED |
| Object | national ice hockey 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: national ice hockey teams | Statement: [EHT, organisesCompetitionFor, national ice hockey teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organisesCompetitionFor Context triple: [EHT, organisesCompetitionFor, national ice hockey teams]
-
A.
competitionOrganized
chosen
Indicates that an entity is responsible for arranging, managing, or hosting a competition or contest involving other participants.
-
B.
organizedCompetitionIn
Indicates that an entity arranged, managed, or hosted a competition that took place in a specified location.
-
C.
organizesChampionship
Indicates that an entity is responsible for planning, coordinating, and managing the execution of a championship event.
-
D.
overseesCompetition
Indicates that one entity has responsibility for supervising, managing, or administering a competition involving another entity.
-
E.
organisedIn
Indicates that an event, activity, or entity is arranged, coordinated, or held within a particular place, context, or organizational framework.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a88b32481909b120349e169c670 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.