Triple
T16064058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Callcott Horsley |
E389688
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Horsley |
E1009224
|
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: Horsley | Statement: [John Callcott Horsley, familyName, Horsley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horsley Context triple: [John Callcott Horsley, familyName, Horsley]
-
A.
Horsley
chosen
Horsley is an English surname borne by various notable individuals across fields such as science, the arts, and public life.
-
B.
Collycroft
Collycroft is a residential area and suburb within the town of Bedworth in Warwickshire, England.
-
C.
Ewart
Ewart is a given name notably borne by the 19th-century British statesman William Ewart Gladstone.
-
D.
Medlicott
Medlicott is the given name of Henry Benedict Medlicott St John, 5th Viscount Bolingbroke, a member of the British peerage.
-
E.
Shadbolt
Shadbolt is a surname most notably associated with Sir Nigel Shadbolt, a prominent British computer scientist and artificial intelligence researcher.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1837b048881908326739bbede756f |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffe47ef6648190bf1fe216e78ef660 |
completed | May 10, 2026, 1:50 a.m. |
Created at: April 10, 2026, 4:57 a.m.