Triple
T19052616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Krafft |
E466298
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Krafft |
E39130
|
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: Krafft | Statement: [Carl Krafft, hasFamilyName, Krafft]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Krafft Context triple: [Carl Krafft, hasFamilyName, Krafft]
-
A.
Krafft
chosen
Krafft is a variant spelling of the surname Kraft, which is of German origin and borne by various notable individuals.
-
B.
Kraushaar
Kraushaar is a surname most notably associated with Raoul Kraushaar, an American film and television composer active in the mid-20th century.
-
C.
Günther
Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
-
D.
Günther
Günther is the zoologist who first formally described the impressed tortoise species Manouria impressa.
-
E.
Ernst
Ernst is a masculine given name of Germanic origin, commonly used in German-speaking and Scandinavian countries.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc03dfa08190924a1b8073364fa1 |
completed | April 20, 2026, 7:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05c556721081908adc6525fbb76ef8 |
completed | May 14, 2026, 12:51 p.m. |
Created at: April 10, 2026, 12:03 p.m.