Triple
T1470282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everett |
E27119
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Eberhard |
E90908
|
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: Eberhard | Statement: [Everett, hasVariant, Eberhard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eberhard Context triple: [Everett, hasVariant, Eberhard]
-
A.
Eberhard
chosen
Eberhard is a German masculine given name of Old High German origin, traditionally meaning "strong boar" or "brave boar."
-
B.
Ruprecht
Ruprecht is a German given name, cognate with Robert, traditionally borne by various historical figures and saints in German-speaking regions.
-
C.
Aribert
Aribert is a Germanic given name, historically borne by medieval nobles and clergy, derived from elements meaning "army" and "bright."
-
D.
Otto the Illustrious
Otto the Illustrious was a powerful 9th–10th century German nobleman of the Liudolfing dynasty whose rule and lineage laid the groundwork for the rise of the Ottonian Holy Roman Emperors.
-
E.
Gerhard
Gerhard is a masculine given name of German origin, historically common in German-speaking 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5d9dd4c8190ba840a9255cd1293 |
completed | March 1, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad1c9fb9e48190b904440cb7229c8f |
completed | March 8, 2026, 6:52 a.m. |
Created at: March 1, 2026, 8:01 p.m.