Triple
T15891004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William H. Fuller |
E385318
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Fuller |
E80984
|
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: Fuller | Statement: [William H. Fuller, hasFamilyName, Fuller]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fuller Context triple: [William H. 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.
Fulman
Fulman is a surname that may refer to individuals such as Jason Fulman and others who share this family name.
-
E.
Flecker
Flecker is the surname of James Elroy Flecker, an early 20th-century British poet and playwright known for his symbolist and exotic verse.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1561e5ac481908ead7de3140c769d |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb7f3c9481908bdde67998263c5e |
completed | May 10, 2026, 2:20 a.m. |
Created at: April 10, 2026, 4:51 a.m.