Triple
T8746507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrews |
E207840
|
entity |
| Predicate | associatedWithGivenName |
P20785
|
FINISHED |
| Object | Thomas |
unclear NED1
|
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: Thomas | Statement: [Andrews, associatedWithGivenName, Thomas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thomas Context triple: [Andrews, associatedWithGivenName, Thomas]
-
A.
Thomas
Thomas is the given name of Tommy Lasorda, the Hall of Fame former manager of the Los Angeles Dodgers.
-
B.
Thomas
Thomas is the given name of Thomas Osborne, 1st Duke of Leeds, a prominent 17th-century English statesman and politician.
-
C.
Thomas
Thomas is the given name of Old Tom Morris, the 19th-century Scottish golfer regarded as a pioneer and four-time Open Championship winner.
-
D.
Thomas
Thomas is the given name of Thomas Pelham-Holles, 1st Duke of Newcastle, a prominent 18th-century British Whig statesman and prime minister.
-
E.
Thomas
Thomas is the given name of Sir Thomas Frankland, a titled member of the British Frankland family.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d75e7c88190a9e78fadb979e1b6 |
completed | March 31, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf43090d388190b6256623805a6348 |
completed | April 3, 2026, 4:33 a.m. |
Created at: March 30, 2026, 6:39 p.m.