Triple
T35605448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ealing, Acton and Shepherd's Bush |
E1028874
|
entity |
| Predicate | containedBorough |
P54716
|
FINISHED |
| Object | London Borough of Ealing |
—
|
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: London Borough of Ealing | Statement: [Ealing, Acton and Shepherd's Bush, containedBorough, London Borough of Ealing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedBorough Context triple: [Ealing, Acton and Shepherd's Bush, containedBorough, London Borough of Ealing]
-
A.
containsEntireBorough
Indicates that one entity fully encompasses the whole geographic area of a borough within its boundaries.
-
B.
containsCityOrBorough
chosen
Indicates that a geographic or administrative area includes, within its boundaries, a specific city or borough.
-
C.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
D.
hasBoroughOrNeighborhood
Indicates that a place is located within, or associated with, a specific borough or neighborhood.
-
E.
incorporatedAsBorough
Indicates that an entity was formally established and granted legal status as a borough.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00c486d394819084fe93d5bb11ea1e |
completed | May 10, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_6a00c39d99d48190a94bfa057213499c |
completed | May 10, 2026, 5:42 p.m. |
Created at: May 3, 2026, 4:05 p.m.