Triple
T21198580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Herbert |
E522390
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Herbert |
—
|
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: Herbert | Statement: [George Herbert, familyName, Herbert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Herbert Context triple: [George Herbert, familyName, Herbert]
-
A.
Herbert
chosen
Herbert is a masculine given name of Germanic origin that has been borne by various notable figures, including U.S. President Herbert Hoover.
-
B.
Herbert
Herbert is an Australian federal electoral division in Queensland that includes areas such as Magnetic Island and parts of the city of Townsville.
-
C.
Harold
Harold is a masculine given name of Old English origin, historically borne by several notable figures including kings and modern public personalities.
-
D.
Hubert
Hubert is a masculine given name of Germanic origin meaning "bright heart" or "shining intellect," historically borne by saints, nobles, and notable public figures.
-
E.
Edwin
Edwin is a masculine given name of Old English origin meaning "rich friend" or "prosperous friend."
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7333d6dec8190bbc66a71b31ea559 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:16 p.m.