Triple
T11519383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerry Goff |
E273120
|
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: [Jerry Goff, familyName, Goff]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goff Context triple: [Jerry Goff, 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.
Davis-Goff
Davis-Goff is the surname of Irish-born writer and screenwriter Annabel Davis-Goff, known for her novels and memoirs often set in Anglo-Irish society.
-
C.
Griese
Griese is a surname most prominently associated with Bob Griese, the Hall of Fame American football quarterback.
-
D.
Goffe
Goffe is a surname variant of "Goff," historically borne by individuals in English-speaking regions.
-
E.
Gage
Gage is a surname of English origin borne by various notable individuals, including historical and contemporary figures.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fcf927081908ef89eff7ad833b0 |
completed | April 10, 2026, 4:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e62540ff4c81909206db0344842c3b |
completed | April 20, 2026, 1:08 p.m. |
Created at: April 8, 2026, 9:36 p.m.