Triple

T16201975
Position Surface form Disambiguated ID Type / Status
Subject Aristi E393222 entity
Predicate hasNearbyVillage P4647 FINISHED
Object Vitsa E393218 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: Vitsa | Statement: [Aristi, hasNearbyVillage, Vitsa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vitsa
Context triple: [Aristi, hasNearbyVillage, Vitsa]
  • A. Vitsa chosen
    Vitsa is a traditional stone-built village in the Zagori region of Epirus, northwestern Greece, known for its preserved architecture and scenic mountain setting.
  • B. Viiala
    Viiala was a former municipality in southern Finland that later became part of the town of Akaa.
  • C. Vehmaa
    Vehmaa is a small rural municipality in southwestern Finland known for its granite quarries and traditional countryside landscape.
  • D. Onega
    Onega is a small town in Arkhangelsk Oblast, northwestern Russia, situated near the mouth of the Onega River on the White Sea coast.
  • E. Ülemsootska
    Ülemsootska is the traditional highest leader of the Seto people, serving as a cultural and communal head within this indigenous Finno-Ugric community of southeastern Estonia and neighboring Russia.
  • 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_69d87f1f5bd08190bd01cac0d5b9d2ef completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e2270b84408190bfbf68f32bfc5b1a completed April 17, 2026, 12:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffff130bcc8190a965d90e123d2dd9 completed May 10, 2026, 3:44 a.m.
Created at: April 10, 2026, 5:03 a.m.