Triple
T13401888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arena Riga |
E319849
|
entity |
| Predicate | homeVenueOf |
P890
|
FINISHED |
| Object | Dinamo 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: Dinamo Riga | Statement: [Arena Riga, homeVenueOf, Dinamo Riga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dinamo Riga Context triple: [Arena Riga, homeVenueOf, Dinamo 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.
Dinamo
Dinamo is a Moscow Metro station named after the nearby Dynamo sports complex and stadium, serving passengers on the Zamoskvoretskaya Line.
-
C.
Dinamo
Dinamo is a professional football club based in Tirana, Albania, known for its historic success in the Albanian football league.
-
D.
Dinamo
Dinamo is a Romanian professional football club based in Bucharest, known for its rich history and passionate fan base.
-
E.
Riga FC
Riga FC is a professional football club based in Riga, Latvia, competing in the Latvian Higher League.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4982e0819087a9fcb2fa88541f |
completed | April 12, 2026, 2:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f73076a7ac8190bd7898edff7d90e8 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:34 p.m.