Triple
T17848437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hennef |
E445725
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Sieg |
—
|
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: Sieg | Statement: [Hennef, locatedOnRiver, Sieg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sieg Context triple: [Hennef, locatedOnRiver, Sieg]
-
A.
Sieg
chosen
The Sieg is a river in western Germany that flows through North Rhine-Westphalia and Rhineland-Palatinate before joining the Rhine.
-
B.
Leiningen
Leiningen is a popular build automation and project management tool for the Clojure programming language, used to manage dependencies, run tasks, and streamline development workflows.
-
C.
Siegl
Siegl is the surname of Zev Siegl, an American entrepreneur best known as one of the co-founders of Starbucks.
-
D.
Reinhard
Reinhard is a masculine German given name historically borne by several notable figures, including high-ranking officials in Nazi Germany.
-
E.
Heinrici
Heinrici is a German surname most notably associated with Gotthard Heinrici, a senior Wehrmacht general during World War II.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffc5fec8190adc66f7b0e264d5f |
completed | April 19, 2026, 8:19 a.m. |
Created at: April 10, 2026, 10:16 a.m.