Triple
T3019324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brentford Dock |
E82413
|
entity |
| Predicate | hasResidentialTenure |
P542
|
FINISHED |
| Object | leasehold apartments |
—
|
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: leasehold apartments | Statement: [Brentford Dock, hasResidentialTenure, leasehold apartments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentialTenure Context triple: [Brentford Dock, hasResidentialTenure, leasehold apartments]
-
A.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
B.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
C.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
-
D.
residenceType
chosen
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
E.
hasExclusiveResidence
Indicates that an entity resides in exactly one specific place and has no other concurrent residences.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a927b608190ba1392498507b237 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.