Triple
T8353943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Coddington |
E196630
|
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 Coddington, hasGivenName, William]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: William Context triple: [William Coddington, 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 the given name of Thomas Fairfax, 1st Lord Fairfax of Cameron, a prominent Parliamentarian general during the English Civil War.
-
D.
Thomas
Thomas is the given name of Thomas Fairfax, 2nd Lord Fairfax of Cameron, a prominent Parliamentary general during the English Civil War.
-
E.
Thomas
Thomas is the given name of Tommy Lasorda, the Hall of Fame former manager of the Los Angeles Dodgers.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804756088190a766e1a486ccfdff |
completed | March 31, 2026, 8:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc75e94288190ba1905dd4ca172dd |
completed | April 2, 2026, 1:33 a.m. |
Created at: March 30, 2026, 5:59 p.m.