Triple
T23387180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rokeby Park, County Durham |
E593914
|
entity |
| Predicate | nearbyCountyBoundary |
P44905
|
FINISHED |
| Object | North Yorkshire |
—
|
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: North Yorkshire | Statement: [Rokeby Park, County Durham, nearbyCountyBoundary, North Yorkshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCountyBoundary Context triple: [Rokeby Park, County Durham, nearbyCountyBoundary, North Yorkshire]
-
A.
hasNearbyCountyBorder
Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
-
B.
hasNearbyCounty
chosen
Indicates that one county is geographically close to or directly adjacent to another county.
-
C.
bordersCountryViaCounty
Indicates that one country shares a border with another country specifically through a county-level administrative region.
-
D.
borderingLocalGovernmentArea
Indicates that one local government area shares a common boundary with another local government area.
-
E.
countyBorder
Indicates that two counties share a common boundary or border with each other.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498fd08819085e90a872d9d0c7a |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.