Triple
T33740190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poplar, London |
E864543
|
entity |
| Predicate | hasNotableHousingEstate |
P203759
|
FINISHED |
| Object | Lansbury Estate |
E1503681
|
NE 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: Lansbury Estate | Statement: [Poplar, London, hasNotableHousingEstate, Lansbury Estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableHousingEstate Context triple: [Poplar, London, hasNotableHousingEstate, Lansbury Estate]
-
A.
notPublicHousingEstate
Indicates that a given housing-related entity is explicitly classified as not being a public housing estate.
-
B.
hasNeighbouringEstate
Indicates that one estate is directly adjacent to or shares a boundary with another estate.
-
C.
hasHouseWithin
Indicates that one entity possesses or is associated with a house that is located within the spatial or administrative boundaries of another entity.
-
D.
hasHouses
Indicates that one entity possesses, controls, or contains one or more houses in relation to another entity or context.
-
E.
isPublicHousing
Indicates that the entity is designated as government-provided or subsidized residential housing intended for public use.
- F. None of above. chosen
Provenance (5 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01e4ba62748190a4756689219b6269 |
completed | May 11, 2026, 2:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a365c8767e081908c401a1b3ee5bcaf |
completed | June 20, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_6a01e3fc2d908190a075c7c1549e5640 |
completed | May 11, 2026, 2:13 p.m. |
| PDg | Predicate description generation | batch_6a01e4b8f30c8190bca53f713ee0f901 |
completed | May 11, 2026, 2:16 p.m. |
Created at: May 1, 2026, 1:44 a.m.