Triple

T15345210
Position Surface form Disambiguated ID Type / Status
Subject Ulvik E366898 entity
Predicate hasDemonym P191 FINISHED
Object Ulvikabu E366898 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: Ulvikabu | Statement: [Ulvik, hasDemonym, Ulvikabu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulvikabu
Context triple: [Ulvik, hasDemonym, Ulvikabu]
  • A. Turgi
    Turgi is a small Swiss municipality in the canton of Aargau, known for its residential character and proximity to the town of Baden.
  • B. Yenikale
    Yenikale is a coastal area near Kerch on the Crimean Peninsula, notable as a World War II amphibious landing site during Soviet operations against German forces.
  • C. Ulvik chosen
    Ulvik is a small scenic municipality and village area in Vestland county, Norway, known for its fjord landscape, fruit orchards, and location along the inner reaches of the Hardanger region.
  • D. Ulvila
    Ulvila is a historic town and municipality in western Finland, located in the Satakunta region along the Kokemäki River.
  • E. Yenakiieve
    Yenakiieve is an industrial city in eastern Ukraine, historically known for its coal mining and metallurgical industries.
  • 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_69d85a1355608190a6673ddb67231d54 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e163a3c8190ab933411372c1573 completed April 16, 2026, 1:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff01f931408190828d87567cecaceb completed May 9, 2026, 9:44 a.m.
Created at: April 10, 2026, 3:17 a.m.