Triple
T9506565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilldale |
E229284
|
entity |
| Predicate | neighbouringSettlement |
P3883
|
FINISHED |
| Object | Parbold |
E43429
|
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: Parbold | Statement: [Hilldale, neighbouringSettlement, Parbold]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parbold Context triple: [Hilldale, neighbouringSettlement, Parbold]
-
A.
Parbold
chosen
Parbold is a village in Lancashire, England, known for its scenic setting near the River Douglas and the Leeds and Liverpool Canal.
-
B.
Shadbolt
Shadbolt is a surname most notably associated with Sir Nigel Shadbolt, a prominent British computer scientist and artificial intelligence researcher.
-
C.
Balderstone
Balderstone is a district and residential area within the Balderstone and Kirkholt ward of Rochdale in Greater Manchester, England.
-
D.
Shephard
Shephard is a variant spelling of the surname "Shepard," commonly used as a family name in English-speaking countries.
-
E.
Balfe
Balfe is a surname of Irish origin borne by various notable individuals in fields such as music, acting, and politics.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9852b7e48190a8f69cbde10d2858 |
completed | April 1, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d178eb63e08190b069faaa0c5dbcb2 |
completed | April 4, 2026, 8:47 p.m. |
Created at: March 30, 2026, 7:57 p.m.