Triple
T11492953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ockendon |
E272459
|
entity |
| Predicate | hasProximityRelation |
P17188
|
FINISHED |
| Object | within commuting distance of central London |
—
|
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: within commuting distance of central London | Statement: [Ockendon, hasProximityRelation, within commuting distance of central London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProximityRelation Context triple: [Ockendon, hasProximityRelation, within commuting distance of central London]
-
A.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
B.
spatialRelation
chosen
Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
-
C.
hasNearbyCommon
Indicates that two entities share at least one common element, feature, or connection that is located within a specified nearby distance or vicinity.
-
D.
isCloseTo
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
E.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a21fb048190acb0960aefd4fe0a |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.