Triple
T21792099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heathcote, Ilkley |
E537994
|
entity |
| Predicate | hasSurroundingAreaName |
P61734
|
FINISHED |
| Object | Heathcote area of Ilkley |
—
|
LITERAL 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: Heathcote area of Ilkley | Statement: [Heathcote, Ilkley, hasSurroundingAreaName, Heathcote area of Ilkley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingAreaName Context triple: [Heathcote, Ilkley, hasSurroundingAreaName, Heathcote area of Ilkley]
-
A.
surroundedAreaColloquialName
chosen
Indicates that an area is commonly referred to by a particular informal or colloquial name by people in the surrounding region.
-
B.
hasNearbyGeographicalArea
Indicates that one geographical area is located in close spatial proximity to another geographical area.
-
C.
hasSurroundings
Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
-
D.
protectedAreaName
Indicates the designated name assigned to a protected area.
-
E.
notableAreaWithin
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f06220bbe0819091cf3b41aa788cc3 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.