Triple
T8357884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reval |
E196723
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Revalen |
E728827
|
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: Revalen | Statement: [Reval, hasAlternativeName, Revalen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Revalen Context triple: [Reval, hasAlternativeName, Revalen]
-
A.
Revalia
chosen
Revalia is an alternative name historically used for the city of Reval, now known as Tallinn, the capital of Estonia.
-
B.
Lierne
Lierne is a sparsely populated municipality in Trøndelag county, Norway, known for its vast wilderness areas, national parks, and rich wildlife.
-
C.
Heltermaa
Heltermaa is a small port village on the eastern coast of Hiiumaa Island in Estonia, serving as a key ferry connection to the mainland.
-
D.
Vytegra
Vytegra is a small town in northwestern Russia known as a regional center near Lake Onega and the White Sea–Baltic Canal.
-
E.
Dinaburg
Dinaburg is the historical name of the Latvian city now known as Daugavpils, an important cultural and economic center in the Latgale region.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb806fa5c88190b23b6b3ee9d6ec6d |
completed | March 31, 2026, 8:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde7bd74fc8190abdb2813d51d79f8 |
completed | April 2, 2026, 3:51 a.m. |
Created at: March 30, 2026, 5:59 p.m.