Triple
T14836083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downend |
E348833
|
entity |
| Predicate | positionRelativeToBristol |
P47202
|
FINISHED |
| Object | northeastern edge |
—
|
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: northeastern edge | Statement: [Downend, positionRelativeToBristol, northeastern edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToBristol Context triple: [Downend, positionRelativeToBristol, northeastern edge]
-
A.
directionFromBristol
chosen
Indicates the cardinal or relative compass direction of one place or object as measured outward starting from Bristol.
-
B.
positionRelativeToCanaryWharf
Indicates the spatial or locational relationship of an entity with respect to Canary Wharf.
-
C.
distanceFromCentralLondon
Indicates the spatial separation or length of travel between a given location and central London.
-
D.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
-
E.
distanceToBristol
Indicates the measured or calculated spatial distance between a given entity and the location of Bristol.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded076ac9c8190a05cabec5e87d207 |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:52 a.m.