Triple
T23800274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manor House |
E588652
|
entity |
| Predicate | hasNearbyHousingEstate |
P103472
|
FINISHED |
| Object | Woodberry Down Estate |
—
|
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: Woodberry Down Estate | Statement: [Manor House, hasNearbyHousingEstate, Woodberry Down Estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHousingEstate Context triple: [Manor House, hasNearbyHousingEstate, Woodberry Down Estate]
-
A.
hasNeighbouringEstate
Indicates that one estate is directly adjacent to or shares a boundary with another estate.
-
B.
nearbyEstate
chosen
Indicates that one estate is located close to another estate in physical space.
-
C.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
D.
hasNearbyDevelopment
Indicates that a development or construction project exists in close physical proximity to the referenced entity.
-
E.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6e0814081908a81e1ede05ab810 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:52 p.m.