Triple
T21437583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priory Country Park |
E528852
|
entity |
| Predicate | isUrbanFringe |
P90278
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Priory Country Park, isUrbanFringe, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanFringe Context triple: [Priory Country Park, isUrbanFringe, true]
-
A.
isUrbanFringeSite
chosen
Indicates that a site is located on the transitional boundary between urban development and surrounding rural or undeveloped areas.
-
B.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
-
C.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
D.
isUrbanForm
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
-
E.
isUrbanizing
Indicates a process in which an area or population becomes more urban in character, typically through increased development, infrastructure, and concentration of people and activities.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8140a1fc8190bedf297cfc4d4841 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6:03 p.m.