Triple
T16323745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Kluge |
E396362
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kluge |
E1006747
|
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: Kluge | Statement: [John Kluge, familyName, Kluge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kluge Context triple: [John Kluge, familyName, Kluge]
-
A.
Kluge
chosen
Kluge is a German surname borne by several notable figures, including military leaders, scholars, and public personalities.
-
B.
Klug
Klug is a surname most notably associated with Aaron Klug, the Nobel Prize–winning chemist and biophysicist known for his work on crystallographic electron microscopy.
-
C.
Cleverly
Cleverly is a Welsh surname most notably associated with former world light-heavyweight boxing champion Nathan Cleverly.
-
D.
the Brilliant
The Brilliant was the epithet of George V of Georgia, a 14th-century king renowned for restoring and strengthening the Georgian kingdom after a period of decline.
-
E.
Klausi
Klausi is a German diminutive form of the male given name Klaus, often used as an affectionate nickname.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b82fe88190a448597b7827f859 |
completed | April 17, 2026, 8:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00260ab4208190900f21cb4f08f926 |
completed | May 10, 2026, 6:30 a.m. |
Created at: April 10, 2026, 5:06 a.m.