Triple
T22795857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulham Palace Road |
E564241
|
entity |
| Predicate | isInPostcodeDistrict |
P75298
|
FINISHED |
| Object | W6 |
—
|
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: W6 | Statement: [Fulham Palace Road, isInPostcodeDistrict, W6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPostcodeDistrict Context triple: [Fulham Palace Road, isInPostcodeDistrict, W6]
-
A.
hasPostcodeDistrictCode
chosen
Indicates that an entity is associated with a specific postcode district code within a postal addressing system.
-
B.
hasPostcodeDistrictsApprox
Indicates that one entity is associated with a set of postcode districts in an approximate or non-exact manner.
-
C.
hasPostcodeSector
Indicates that an entity is associated with a specific postcode sector within a postal addressing system.
-
D.
hasNeighbouringPostcodeDistrict
Indicates that one postcode district is geographically adjacent to or directly borders another postcode district.
-
E.
isInnerDistrictOf
Indicates that one district is geographically or administratively located within and subordinate to another, larger district.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cd8e0c4819086da0488bea56a34 |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:30 p.m.