Triple
T24554680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Darlington |
E607478
|
entity |
| Predicate | borderingCeremonialCounty |
P115528
|
FINISHED |
| Object | County Durham |
—
|
NE NERFINISHED |
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: County Durham | Statement: [Borough of Darlington, borderingCeremonialCounty, County Durham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingCeremonialCounty Context triple: [Borough of Darlington, borderingCeremonialCounty, County Durham]
-
A.
bordersCeremonialCounty
chosen
Indicates that one ceremonial county shares a boundary with another ceremonial county.
-
B.
ceremonialCounty
Indicates that one entity is the ceremonial (non-administrative, often traditional or representational) county associated with the other entity.
-
C.
sharesCeremonialCountyWith
Indicates that two entities are located within the same ceremonial county.
-
D.
borderingAuthorityOf
Indicates that one authority’s jurisdiction directly touches or shares a boundary with another authority’s jurisdiction.
-
E.
borderingConstituency
Indicates that one political constituency shares a common boundary with another constituency.
- F. None of above.
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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f13d4c81909ffecf8c26d272f0 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.