Triple

T16893690
Position Surface form Disambiguated ID Type / Status
Subject Dzūkija E424239 entity
Predicate historicalName P65 FINISHED
Object Dainava E1006945 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: Dainava | Statement: [Dzūkija, historicalName, Dainava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dainava
Context triple: [Dzūkija, historicalName, Dainava]
  • A. Dainava chosen
    Dainava is a historical region in the territory of present-day Lithuania and northeastern Poland, traditionally associated with the Baltic Yotvingian and Lithuanian tribes.
  • B. Ristna
    Ristna is a small settlement in Estonia located on the island of Hiiumaa, known for its coastal scenery and proximity to the historic Ristna Lighthouse.
  • C. Velkua
    Velkua is a former island municipality in southwestern Finland known for its coastal archipelago landscape in the Baltic Sea.
  • D. Nednai
    Nednai is an alternate name for the Nednhi Apache, a subgroup of the Chiricahua Apache people historically living in northern Mexico and the U.S. Southwest.
  • E. Dausa
    Dausa is a town and district headquarters in the Indian state of Rajasthan, known for its historical forts, stepwells, and proximity to Jaipur.
  • 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_69d889da3e8c8190a2b118f383f0beac completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3bbc6b97c8190b18aca477d6ef647 completed April 18, 2026, 5:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c7aa83bc8190832d2f3903ce0081 completed May 10, 2026, 6 p.m.
Created at: April 10, 2026, 5:29 a.m.