Triple
T14743498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodor Körner |
E346408
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Körner |
E170519
|
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: Körner | Statement: [Theodor Körner, familyName, Körner]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Körner Context triple: [Theodor Körner, familyName, Körner]
-
A.
Körner
chosen
Körner is a German surname borne by various notable figures in fields such as literature, music, and politics.
-
B.
Hermann Körner
Hermann Körner was a notable individual who carried the German surname Körner, though specific widely known biographical details about him are not well documented.
-
C.
Reinhard Körner
Reinhard Körner is a German Catholic theologian and Carmelite priest known for his work in spirituality and religious education.
-
D.
Finklehoffe
Finklehoffe is the surname of Fred F. Finklehoffe, an American screenwriter and film producer active in Hollywood’s mid-20th century studio era.
-
E.
Sindorf
Sindorf is a district of the town of Kerpen in North Rhine-Westphalia, Germany.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7367a1c819081082cc355e385fa |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb93e94c8190beba605e26d4552c |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:30 a.m.