Triple

T4552757
Position Surface form Disambiguated ID Type / Status
Subject Puch bei Hallein E120404 entity
Predicate locatedNear P294 FINISHED
Object Elsbethen E120403 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: Elsbethen | Statement: [Puch bei Hallein, locatedNear, Elsbethen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elsbethen
Context triple: [Puch bei Hallein, locatedNear, Elsbethen]
  • A. Elsbethen chosen
    Elsbethen is a municipality in the Austrian state of Salzburg, located just south of the city of Salzburg and known for its scenic Alpine surroundings.
  • B. Eythorne
    Eythorne is a small village in Kent, England, known for its rural character and location near the port town of Dover.
  • C. Heseltine
    Heseltine is a surname most prominently associated with Michael Heseltine, a senior British Conservative politician and former Deputy Prime Minister.
  • D. Maidenbower
    Maidenbower is a residential neighbourhood and modern housing development located on the eastern side of Crawley in West Sussex, England.
  • E. Tattersett
    Tattersett is a small village and civil parish in Norfolk, England, situated in a rural area of the county.
  • 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_69bd4636f1648190a701445c2fcd9c17 completed March 20, 2026, 1:05 p.m.
NER Named-entity recognition batch_69bd581160e08190b715a8ce5c3e6c9b completed March 20, 2026, 2:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdb95b01b0819094a600752e41aa09 completed March 20, 2026, 9:17 p.m.
Created at: March 20, 2026, 1:09 p.m.