Triple

T19472855
Position Surface form Disambiguated ID Type / Status
Subject Planken E487167 entity
Predicate sharesNationalGovernmentWith P48855 FINISHED
Object Eschen 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: Eschen | Statement: [Planken, sharesNationalGovernmentWith, Eschen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eschen
Context triple: [Planken, sharesNationalGovernmentWith, Eschen]
  • A. Eschen chosen
    Eschen is a municipality in northern Liechtenstein known for its residential character and role as one of the country’s larger population centers.
  • B. Escheburg
    Escheburg is a small municipality in the district of Herzogtum Lauenburg in Schleswig-Holstein, northern Germany.
  • C. Tettenweis
    Tettenweis is a small Bavarian village in Germany known as the birthplace of the Symbolist painter Franz von Stuck.
  • D. Rottenegg
    Rottenegg is a small village that forms one of the local subdivisions of the Bavarian town of Geisenfeld in Germany.
  • E. Meisenthal
    Meisenthal is a village in northeastern France renowned for its historic glassmaking tradition and cultural heritage.
  • 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_69d8e8d924388190b847cb15bb3d0aff completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e633ea604c8190a2feacb709b7ca27 completed April 20, 2026, 2:10 p.m.
Created at: April 10, 2026, 1:39 p.m.