Triple
T1296973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Championship League |
E27674
|
entity |
| Predicate | notableClub |
P8182
|
FINISHED |
| Object | Dynamo Riga |
E114622
|
NE 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: Dynamo Riga | Statement: [Soviet Championship League, notableClub, Dynamo Riga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dynamo Riga Context triple: [Soviet Championship League, notableClub, Dynamo Riga]
-
A.
Dinamo Riga
chosen
Dinamo Riga is a professional ice hockey club based in Riga, Latvia, known for competing in top European and international leagues.
-
B.
Riga FC
Riga FC is a professional football club based in Riga, Latvia, competing in the Latvian Higher League.
-
C.
Dynamo Moscow
Dynamo Moscow is a prominent Russian professional ice hockey club based in Moscow, historically known for developing elite players such as Alex Ovechkin.
-
D.
Dynamo Minsk
Dynamo Minsk is a professional sports club from Minsk, Belarus, best known for its football team competing in the country’s top league and European competitions.
-
E.
Dynamo Bucharest
Dynamo Bucharest is a prominent Romanian sports club best known for its historically successful football team based in Bucharest.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0f591ec819084f01f518c332880 |
completed | March 1, 2026, 10:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acd4729af08190a6de5388dab69fee |
completed | March 8, 2026, 1:44 a.m. |
Created at: March 1, 2026, 7:51 p.m.