Triple

T19251733
Position Surface form Disambiguated ID Type / Status
Subject Andematunnum E481407 entity
Predicate connectedTo P37 FINISHED
Object Vesontio NE NERFINISHED

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: Vesontio | Statement: [Andematunnum, connectedTo, Vesontio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vesontio
Context triple: [Andematunnum, connectedTo, Vesontio]
  • A. Vesontio chosen
    Vesontio was the ancient Roman city that later became Besançon, an important urban and military center in the province of Germania Superior.
  • B. Vanajavesi
    Vanajavesi is a prominent lake in southern Finland known for its scenic waterways, cultural heritage, and role in the Kokemäenjoki river basin.
  • C. Vehmaa
    Vehmaa is a small rural municipality in southwestern Finland known for its granite quarries and traditional countryside landscape.
  • D. Viiala
    Viiala was a former municipality in southern Finland that later became part of the town of Akaa.
  • E. Viimsi
    Viimsi is a rapidly developing suburban municipality in northern Estonia, located just northeast of the capital city Tallinn.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8cd9d1081908a181d02b88b59b8 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fb30bf6c819094c44aceb544a023 completed April 20, 2026, 10:08 a.m.
Created at: April 10, 2026, 1:28 p.m.