Triple

T13583826
Position Surface form Disambiguated ID Type / Status
Subject Hunedoara E324493 entity
Predicate locatedOn P40 FINISHED
Object Cerna River E359915 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: Cerna River | Statement: [Hunedoara, locatedOn, Cerna River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cerna River
Context triple: [Hunedoara, locatedOn, Cerna River]
  • A. Cerna River chosen
    The Cerna River is a river in southwestern Romania that flows through the historic spa town of Băile Herculane before joining the Danube.
  • B. Crasna River
    The Crasna River is a tributary watercourse in eastern Romania that feeds into the larger Bârlad River system.
  • C. Crna River
    The Crna River is a significant river in North Macedonia that flows through the Pelagonia region before joining the Axios (Vardar) River.
  • D. Târnava Mare River
    The Târnava Mare River is a significant river in central Romania that flows through the historical region of Transylvania before joining the Mureș River.
  • E. Crișul Alb River
    The Crișul Alb River is a significant river in western Romania that flows through the Apuseni Mountains and the Crișana region before crossing into Hungary.
  • 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_69d80769100c819099111274614f5ed2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb03310fc819092a56b9f2d73f560 completed April 12, 2026, 2:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe387c02108190badf9b5051cd9c7a completed May 8, 2026, 7:24 p.m.
Created at: April 9, 2026, 9:49 p.m.