Triple
T4961667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mestia |
E111421
|
entity |
| Predicate | localLanguage |
P1252
|
FINISHED |
| Object | Svan |
E278111
|
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: Svan | Statement: [Mestia, localLanguage, Svan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Svan Context triple: [Mestia, localLanguage, Svan]
-
A.
Svan people
chosen
The Svan people are an indigenous ethnic subgroup of Georgians from the remote, mountainous Svaneti region of northwestern Georgia, known for their distinct culture, traditions, and historical tower villages.
-
B.
Etnedal
Etnedal is a rural municipality in Innlandet county, Norway, known for its forested valleys, agriculture, and outdoor recreation.
-
C.
Svear
Svear were an ancient North Germanic people of central Sweden who formed a core part of the early Swedish kingdom.
-
D.
Svir
Svir is a river in northwestern Russia that connects Lake Onega with Lake Ladoga and forms part of the Volga–Baltic Waterway.
-
E.
Svan culture
Svan culture is the traditional highland culture of the Svan people in northwestern Georgia, known for its ancient language, distinctive tower architecture, polyphonic singing, and rich mountain customs.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71dc06a48190827d54a5c0351aab |
completed | March 20, 2026, 4:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be81ea8cc08190af40098ca99364f1 |
completed | March 21, 2026, 11:32 a.m. |
Created at: March 20, 2026, 1:32 p.m.