Triple
T18921001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buckhurst Hill |
E462853
|
entity |
| Predicate | withinMetropolitanGreenBelt |
P37570
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Buckhurst Hill, withinMetropolitanGreenBelt, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinMetropolitanGreenBelt Context triple: [Buckhurst Hill, withinMetropolitanGreenBelt, yes]
-
A.
withinGreenBelt
Indicates that one entity is located inside the designated green belt area associated with another entity or region.
-
B.
isPartOfMetropolitanGreenBelt
chosen
Indicates that an area lies within a designated metropolitan green belt intended to limit urban sprawl and protect open land around a city.
-
C.
withinLondonCommuterBelt
Indicates that a location lies within the geographic area from which people commonly commute into London for work or study.
-
D.
containsMetropolitanBorough
Indicates that an administrative area includes within its boundaries one or more metropolitan boroughs as subordinate units.
-
E.
hasOuterLondonBorough
Indicates that an entity is associated with, located in, or administered by a borough that is part of Outer London.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b3b93c819085032d8251a43ca8 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.