Triple
T8306301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Goff of Chieveley |
E194471
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Goff |
E211687
|
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: Goff | Statement: [Lord Goff of Chieveley, familyName, Goff]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goff Context triple: [Lord Goff of Chieveley, familyName, Goff]
-
A.
Goff
chosen
Goff is a surname most notably associated with Bruce Goff, an innovative American architect known for his unconventional and organic designs.
-
B.
Griese
Griese is a surname most prominently associated with Bob Griese, the Hall of Fame American football quarterback.
-
C.
Gage
Gage is a surname of English origin borne by various notable individuals, including historical and contemporary figures.
-
D.
Geisman
Geisman is the birth surname of American actress June Allyson, a popular film star of the 1940s and 1950s.
-
E.
Lohse
Lohse is a German surname borne by various notable individuals in fields such as science, sports, and the arts.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f293db08190912e5e8bb7e940cf |
completed | March 31, 2026, 8 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd955100448190862fd52d660585fd |
completed | April 1, 2026, 9:59 p.m. |
Created at: March 30, 2026, 5:54 p.m.