Triple

T20562301
Position Surface form Disambiguated ID Type / Status
Subject Ludwigsburg district E504872 entity
Predicate hasRiver P165 FINISHED
Object Enz E88874 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: Enz | Statement: [Ludwigsburg district, hasRiver, Enz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Enz
Context triple: [Ludwigsburg district, hasRiver, Enz]
  • A. Enz chosen
    The Enz is a river in southwestern Germany that flows through the Black Forest region before joining the Neckar River.
  • B. ENK
    ENK is the ICAO airline designator assigned to Equair, an Ecuadorian commercial airline.
  • C. ENZV
    ENZV is the ICAO airport code for Stavanger Airport, Sola, a major international airport serving the Stavanger region in southwestern Norway.
  • D. Enez
    Enez is a small Turkish town on the Aegean coast, historically known as the ancient Greek city of Ainos.
  • E. Enkomi
    Enkomi is an important Late Bronze Age archaeological site on Cyprus, identified by many scholars with the ancient city of Alashiya.
  • 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_69e0b4b6587c8190aee63dc7cff244ea completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a79f906c819081163de9649ccb17 completed April 20, 2026, 10:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a08acdac8008190a7a61d46f7041cf4 completed May 16, 2026, 5:43 p.m.
Created at: April 16, 2026, 11:39 a.m.