Triple
T2105580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Holme |
E37186
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Holme |
E37186
|
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: Holme | Statement: [Edward Holme, hasSurname, Holme]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holme Context triple: [Edward Holme, hasSurname, Holme]
-
A.
Holme
chosen
Holme is a surname and place name of English origin that appears as a variant of the more common name "Holmes."
-
B.
Reeds Holme
Reeds Holme is a small locality within the Rossendale borough of Lancashire, England, known primarily as a residential area in the South Pennines.
-
C.
Minstead
Minstead is a small village in Hampshire, England, best known as the burial place of Sir Arthur Conan Doyle.
-
D.
Shudehill
Shudehill is a central district in Manchester, England, known for its major bus and tram interchange and proximity to the city’s main shopping and commercial areas.
-
E.
Killingholme
Killingholme is a village and civil parish in North Lincolnshire, England, known for its historical military and naval associations.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbadcd4a081909d60b9b241950335 |
completed | March 7, 2026, 5:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae306bee8881908c62306fb1f6aea1 |
completed | March 9, 2026, 2:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.