Triple
T32882546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langley |
E841102
|
entity |
| Predicate | hasPostcodeAreaNow |
P198146
|
FINISHED |
| Object | WD |
—
|
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: WD | Statement: [Langley, hasPostcodeAreaNow, WD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostcodeAreaNow Context triple: [Langley, hasPostcodeAreaNow, WD]
-
A.
hasPostcodeAreasAlong
Indicates that a geographic feature or route is associated with, or passes through, specific postcode areas along its extent.
-
B.
hasPostcodeDistrictCode
Indicates that an entity is associated with a specific postcode district code within a postal addressing system.
-
C.
hasPostcodeSector
Indicates that an entity is associated with a specific postcode sector within a postal addressing system.
-
D.
hasPostcodeDistrictsApprox
Indicates that one entity is associated with a set of postcode districts in an approximate or non-exact manner.
-
E.
hasPostcodeFormat
Indicates that a location or address follows a specific postal code pattern or structure defined by a given standard.
- F. None of above. chosen
Provenance (4 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fecd091abc8190872974de731a80fa |
completed | May 9, 2026, 5:58 a.m. |
Created at: May 1, 2026, 1:18 a.m.