Triple
T17421775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inge König |
E423633
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | König |
—
|
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: König | Statement: [Inge König, hasSurname, König]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: König Context triple: [Inge König, hasSurname, König]
-
A.
König
chosen
König is a German-language surname borne by numerous individuals, including notable figures in fields such as religion, science, and the arts.
-
B.
Kœnig
Kœnig is a French surname most notably associated with figures such as General Marie-Pierre Kœnig, a prominent military leader during World War II.
-
C.
Koning
Koning is a Dutch surname and term meaning “king,” commonly used in the Netherlands and Belgium.
-
D.
Kaiservilla
Kaiservilla is a former imperial summer residence in Bad Ischl, Austria, best known as the retreat of Emperor Franz Joseph I and Empress Elisabeth of Austria.
-
E.
Gegenkönig
Gegenkönig is the German term for a rival or counter-king who claims the throne in opposition to a reigning monarch, especially in the context of medieval German history.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44237f2cc819083ca0e7e00d828fb |
completed | April 19, 2026, 2:47 a.m. |
Created at: April 10, 2026, 5:46 a.m.