Triple
T35812473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeading |
E1035267
|
entity |
| Predicate | partOfBoroughRegion |
P202678
|
FINISHED |
| Object | Hayes and Yeading area |
—
|
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: Hayes and Yeading area | Statement: [Yeading, partOfBoroughRegion, Hayes and Yeading area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfBoroughRegion Context triple: [Yeading, partOfBoroughRegion, Hayes and Yeading area]
-
A.
wasBoroughOf
Indicates that one place previously held the administrative or territorial status of a borough within another jurisdiction.
-
B.
locatedInBoroughCommunityDistrict
Indicates that something is situated within a specific borough community district.
-
C.
isCentralBoroughOf
Indicates that a borough serves as the primary or central administrative or geographic district of a specified city or region.
-
D.
locatedInFormerBorough
Indicates that an entity is or was situated within the geographic area of a borough that no longer exists as an administrative unit.
-
E.
operatedInBorough
Indicates that an entity conducted its operations or activities within the geographic area of a specific borough.
- F. None of above. chosen
Provenance (4 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00ac5654a0819090701f61a5802d64 |
completed | May 10, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_6a00ab94b5e881909e15d1342e5f43be |
completed | May 10, 2026, 4 p.m. |
| PDg | Predicate description generation | batch_6a00ac559e088190be06fa1af5f24712 |
completed | May 10, 2026, 4:03 p.m. |
Created at: May 3, 2026, 4:06 p.m.