Triple
T214983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynamo Moscow |
E4798
|
entity |
| Predicate | homeCountryLeague |
P3509
|
FINISHED |
| Object | Russian 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 ice hockey system | Statement: [Dynamo Moscow, homeCountryLeague, Russian ice hockey system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCountryLeague Context triple: [Dynamo Moscow, homeCountryLeague, Russian ice hockey system]
-
A.
countryOfLeague
chosen
Indicates the country in which a given league is based or officially belongs.
-
B.
homeLeague
Indicates that a sports team primarily competes in, or is officially associated with, a particular league as its main organizational affiliation.
-
C.
hostCountryNOC
Indicates that a National Olympic Committee (NOC) is the official host country organization for a particular Olympic Games or sporting event.
-
D.
originLeague
Indicates the sports league or competition from which an entity (such as a team, player, or event) originally comes or is associated.
-
E.
hostsLeague
Indicates that one entity serves as the organizing or venue-providing host for a particular 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.