Triple
T20180091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bampfylde Fuller |
E492703
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Fuller |
—
|
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: Fuller | Statement: [Bampfylde Fuller, hasFamilyName, Fuller]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fuller Context triple: [Bampfylde Fuller, hasFamilyName, Fuller]
-
A.
Fuller
chosen
Fuller is a surname of English origin borne by numerous notable individuals across fields such as film, architecture, literature, and politics.
-
B.
Furner
Furner is a rural locality situated within South Australia's Wattle Range Council area.
-
C.
Fowler
Fowler is a surname of English origin borne by numerous notable individuals across fields such as engineering, politics, sports, and the arts.
-
D.
Farrar
Farrar is a surname most notably associated with American musician and songwriter Jay Farrar, co-founder of the influential alternative country band Uncle Tupelo.
-
E.
Fulman
Fulman is a surname that may refer to individuals such as Jason Fulman and others who share this family name.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668edf27881909820f9103e72533e |
completed | April 20, 2026, 5:57 p.m. |
Created at: April 11, 2026, 11:36 p.m.