Triple
T5040605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riga FC |
E113534
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | Riga FC |
E113534
|
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: Riga FC | Statement: [Riga FC, shortName, Riga FC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riga FC Context triple: [Riga FC, shortName, Riga FC]
-
A.
Riga FC
chosen
Riga FC is a professional football club based in Riga, Latvia, competing in the Latvian Higher League.
-
B.
Dinamo Riga
Dinamo Riga is a professional ice hockey club based in Riga, Latvia, known for competing in top European and international leagues.
-
C.
FC Gomel
FC Gomel is a professional football club from Gomel, Belarus, that competes in the Belarusian football league system.
-
D.
BC Lietkabelis Panevėžys
BC Lietkabelis Panevėžys is a professional basketball club from Panevėžys, Lithuania, competing in the country’s top basketball league and European competitions.
-
E.
Lokomotiv Moscow
Lokomotiv Moscow is a major Russian professional football club from Moscow, known for competing in the Russian Premier League and being one of the city’s traditional powerhouses.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73dd27fc8190817e53311ea3f706 |
completed | March 20, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be9c8414288190bf53a40033aa70ea |
completed | March 21, 2026, 1:26 p.m. |
Created at: March 20, 2026, 1:37 p.m.