Triple
T30281918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whalley Range ward |
E770119
|
entity |
| Predicate | isResidentialAreaWardFor |
P76280
|
FINISHED |
| Object | Whalley Range residential area |
—
|
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: Whalley Range residential area | Statement: [Whalley Range ward, isResidentialAreaWardFor, Whalley Range residential area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResidentialAreaWardFor Context triple: [Whalley Range ward, isResidentialAreaWardFor, Whalley Range residential area]
-
A.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
B.
isInResidentialArea
Indicates that something is located within a residential area, such as a neighborhood or zone primarily designated for housing.
-
C.
isWardOf
Indicates that one entity is under the guardianship, protection, or legal care of another entity as their ward.
-
D.
locatedInCityWard
chosen
Indicates that one entity is situated within the administrative boundaries of a specific city ward.
-
E.
isResidentialRegionPart
Indicates that one residential region is a constituent or included part of another, larger residential region.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681057b688190b8058e4cd2b2235a |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:45 p.m.