Triple
T16066855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downshire House |
E389755
|
entity |
| Predicate | associatedWithTitle |
P914
|
FINISHED |
| Object | Downshire |
E1193280
|
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: Downshire | Statement: [Downshire House, associatedWithTitle, Downshire]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Downshire Context triple: [Downshire House, associatedWithTitle, Downshire]
-
A.
Downshire
chosen
Downshire is a historic territorial designation in Ireland associated with the noble title of Marquess of Downshire.
-
B.
Hantshire
Hantshire is an old historic name formerly used for the English county now known as Hampshire.
-
C.
Downlands
Downlands is a residential suburb within the coastal city of Burnie in north-west Tasmania, Australia.
-
D.
Darbyshire
Darbyshire is an English surname of likely toponymic origin, associated with individuals such as the architect and playwright Alfred Darbyshire.
-
E.
Darfield
Darfield is a village in South Yorkshire, England, historically associated with coal mining and situated near the River Dearne.
- 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_69e1837ca628819081dfc439fe322d58 |
completed | April 17, 2026, 12:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb8cca308190875432a5cf5f8616 |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 10, 2026, 4:57 a.m.