Triple
T16420436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everhard |
E398801
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Everhart |
E667471
|
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: Everhart | Statement: [Everhard, hasVariant, Everhart]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Everhart Context triple: [Everhard, hasVariant, Everhart]
-
A.
Everhart
chosen
Everhart is a surname of English and German origin that is borne by various notable individuals across fields such as politics, sports, and the arts.
-
B.
Silloo Bode
Silloo Bode was the wife of Indian Field Marshal Sam Manekshaw and a member of the Parsi community.
-
C.
Vizenor
Vizenor is the surname of Gerald Vizenor, a prominent Native American writer, scholar, and critical theorist known for his work on Native American literature and postmodernism.
-
D.
Koldewey
Koldewey is a German surname most notably associated with Robert Koldewey, the archaeologist who led the excavation of ancient Babylon.
-
E.
Haldemann
Haldemann is a surname, likely of Germanic origin, that serves as a variant spelling of the name Haldeman.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328f5c1bc8190a679f35bd6c0bc97 |
completed | April 18, 2026, 6:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c6e882c81908fae034f1b75b7ee |
completed | May 10, 2026, 8:06 a.m. |
Created at: April 10, 2026, 5:09 a.m.