Triple
T38529353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battersea Power Station Estate |
E923316
|
entity |
| Predicate | hasMixedUse |
P33911
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Battersea Power Station Estate, hasMixedUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMixedUse Context triple: [Battersea Power Station Estate, hasMixedUse, true]
-
A.
hasZoningMix
Indicates that an area or property is subject to a combination of different zoning designations or land-use categories.
-
B.
hasHousingMix
Indicates the composition or distribution of different housing types or tenures associated with an entity.
-
C.
hasHybridUses
Indicates that an entity is used in both traditional (e.g., physical or analog) and modern or alternative (e.g., digital, renewable, or mixed-mode) ways or contexts.
-
D.
propertyTypeMix
chosen
Indicates that an entity involves or consists of a combination of different types of properties rather than a single uniform property type.
-
E.
hasBlendOfResidentialAndIndustrialAreas
Indicates that a location contains a mix of both residential and industrial zones or land uses.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:32 p.m.