Triple
T21814825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizur Goodrich |
E538576
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Elizur |
—
|
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: Elizur | Statement: [Elizur Goodrich, givenName, Elizur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elizur Context triple: [Elizur Goodrich, givenName, Elizur]
-
A.
Elizur
chosen
Elizur is a masculine given name of Hebrew origin, historically borne by several notable figures in early American history.
-
B.
Eliphalet
Eliphalet is a masculine given name of Hebrew origin, historically used in English-speaking countries, particularly in religious and colonial American contexts.
-
C.
Dedan
Dedan is a biblical figure mentioned in the Hebrew Bible as a descendant of Abraham through Keturah and associated with an Arabian tribe or region known for trade.
-
D.
Amasa
Amasa is a biblical military commander mentioned in the Old Testament, notably involved in the power struggles during King David’s reign.
-
E.
Reuel
Reuel is a biblical figure identified as another name for Jethro, the Midianite priest and father-in-law of Moses.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc99bbc8190bf074930f361af7d |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 16, 2026, 6:54 p.m.