Triple
T10537886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennington Lane |
E248618
|
entity |
| Predicate | isInPostalArea |
P39182
|
FINISHED |
| Object | SE11 |
—
|
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: SE11 | Statement: [Kennington Lane, isInPostalArea, SE11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPostalArea Context triple: [Kennington Lane, isInPostalArea, SE11]
-
A.
postalAreaIncludes
Indicates that a given postal area geographically contains or covers another specified location or region.
-
B.
isInArea
chosen
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
C.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
D.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
E.
hasPostalAssociationWith
Indicates a relationship in which one entity is connected to another through postal services, such as mail handling, delivery, routing, or shared postal operations.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a56133c819088285522e64831f7 |
completed | April 7, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:31 p.m.