Triple
T17926977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald D. Engen |
E448221
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Engen |
—
|
NE NERFINISHED |
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: Engen | Statement: [Donald D. Engen, familyName, Engen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Engen Context triple: [Donald D. Engen, familyName, Engen]
-
A.
Engen
chosen
Engen is a surname of Norwegian origin borne by various notable individuals across fields such as aviation, sports, and public service.
-
B.
Engey
Engey is a small uninhabited island in Iceland, located just off the coast of Reykjavík in Faxaflói Bay.
-
C.
Engen era
The Engen era was a Japanese historical period name (nengō) used by the Southern Court during the Nanboku-chō period in the early 14th century.
-
D.
Enenga
Enenga is a dialect of the Myene language spoken by communities in Gabon.
-
E.
Engi
Engi was a Japanese era name (nengō) of the early 10th century, notable for its association with Emperor Daigo’s reign and significant political and cultural developments in the Heian period.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a54f29a88190b035d8473765bde5 |
completed | April 19, 2026, 9:50 a.m. |
Created at: April 10, 2026, 10:20 a.m.