Triple
T15169024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Eckart |
E362435
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Eckart |
E1099539
|
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: Eckart | Statement: [Carl Eckart, hasFamilyName, Eckart]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eckart Context triple: [Carl Eckart, hasFamilyName, Eckart]
-
A.
Eckart
chosen
Eckart is a German surname most notably associated with Dietrich Eckart, an early 20th-century nationalist writer and influential figure in the rise of Nazism.
-
B.
Eckstine
Eckstine is the surname of Billy Eckstine, the influential American jazz and pop singer and bandleader known for his rich baritone voice and pioneering big band.
-
C.
Estermann
Estermann is a surname most notably associated with mathematician Theodor Estermann, known for his contributions to analytic number theory.
-
D.
Eisler
Eisler is a German-language surname most notably associated with composer Hanns Eisler, known for his politically engaged music and collaborations with Bertolt Brecht.
-
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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064dba588190a4341775b472a6d3 |
completed | April 15, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec889c3408190bdfc75ce72dd5a62 |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 10, 2026, 3:08 a.m.