Triple
T2358815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Hayes Fogg |
E47221
|
entity |
| Predicate | hasGivenName |
P17
|
FINISHED |
| Object | William |
E772
|
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: William | Statement: [William Hayes Fogg, hasGivenName, William]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: William Context triple: [William Hayes Fogg, hasGivenName, William]
-
A.
William
chosen
William is a common masculine given name of Germanic origin, widely used in English-speaking countries.
-
B.
Thomas
Thomas is the given name of Thomas Cranmer, the 16th-century Archbishop of Canterbury and a leading figure in the English Reformation.
-
C.
Thomas
Thomas is a common masculine given name of Aramaic origin, widely used in English-speaking and many other cultures.
-
D.
Thomas
Thomas is the given name of Confederate General "Stonewall" Jackson, a prominent military leader during the American Civil War.
-
E.
Thomas
Thomas is a common surname of English and Welsh origin, derived from the given name Thomas and borne by numerous notable individuals worldwide.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc720b9048190a5d3b19e5e1f373a |
completed | March 7, 2026, 6:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae9638ef948190adf945aba42fac76 |
completed | March 9, 2026, 9:43 a.m. |
Created at: March 4, 2026, 7:55 p.m.