Triple
T15824568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August Eberstein |
E383703
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Eberstein |
E383703
|
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: Eberstein | Statement: [August Eberstein, familyName, Eberstein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eberstein Context triple: [August Eberstein, familyName, Eberstein]
-
A.
Eberstein
chosen
Eberstein is a German surname most notably associated with August Eberstein, a co-founder of the Montblanc pen company.
-
B.
Eckstein
Eckstein is a German-origin surname borne by various notable individuals across fields such as sports, academia, and the arts.
-
C.
Elliger
Elliger is a German-language surname most notably associated with the Baroque painter Karl Elliger.
-
D.
Eberl
Eberl is a German-language surname of Austrian and Bavarian origin borne by various notable individuals.
-
E.
Seibert
Seibert is a German-origin surname borne by various notable individuals across fields such as sports, science, and the arts.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e5f46748190acb46cc482501307 |
completed | April 16, 2026, 5:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff999bba548190a39adc2d0e11c605 |
completed | May 9, 2026, 8:31 p.m. |
Created at: April 10, 2026, 4:49 a.m.