Triple
T7470920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everard |
E176500
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Everhardt |
E398802
|
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: Everhardt | Statement: [Everard, relatedName, Everhardt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Everhardt Context triple: [Everard, relatedName, Everhardt]
-
A.
Godehart
Godehart is a German given name, serving as a variant form of the name Gotthard.
-
B.
Mordaunt
Mordaunt is a vengeful and fanatical antagonist in Alexandre Dumas’ d'Artagnan romances, known as the ruthless son of Milady de Winter who seeks to destroy the musketeers.
-
C.
Eberhardt
chosen
Eberhardt is a German masculine given name and surname derived from Old High German elements meaning "boar" and "brave" or "hardy."
-
D.
Burkhard
Burkhard is a Germanic-origin surname found in various European countries and among their diasporas.
-
E.
Armgard
Armgard is a feminine given name of German origin, historically borne by European nobility such as Armgard von Cramm, the mother of Prince Bernhard of Lippe-Biesterfeld.
- 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4145d608190bd93239f04f7da41 |
completed | March 27, 2026, 9:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8347b36388190989d2bcbe3f747bf |
completed | March 28, 2026, 8:05 p.m. |
Created at: March 27, 2026, 3:41 p.m.