Triple

T22793189
Position Surface form Disambiguated ID Type / Status
Subject Feldkirchen (Austria) E564167 entity
Predicate locatedOn P40 FINISHED
Object Glan River 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: Glan River | Statement: [Feldkirchen (Austria), locatedOn, Glan River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Glan River
Context triple: [Feldkirchen (Austria), locatedOn, Glan River]
  • A. Glan River chosen
    The Glan River is a watercourse in the Austrian state of Carinthia that flows through the city of Klagenfurt before joining the Gurk River.
  • B. Ager River
    The Ager River is a watercourse in Upper Austria that flows through the Salzkammergut region and ultimately joins the Traun River.
  • C. Viar River
    The Viar River is a tributary watercourse in southwestern Spain that feeds into the Guadalquivir River system.
  • D. Vils River
    The Vils River is a tributary waterway in the Alpine region of Austria and Germany that flows through scenic valleys before joining the Lech River.
  • E. Orbieu River
    The Orbieu River is a watercourse in southern France that flows through the Aude department and joins the Aude River.
  • 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_69e2458185f88190b0045227ee420411 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17cd751f081909c7907c96c9906ea completed April 29, 2026, 3:36 a.m.
Created at: April 17, 2026, 3:30 p.m.