Triple
T8179688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consett |
E191026
|
entity |
| Predicate | directionFromNewcastleUponTyne |
P44617
|
FINISHED |
| Object | south-west |
—
|
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: south-west | Statement: [Consett, directionFromNewcastleUponTyne, south-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromNewcastleUponTyne Context triple: [Consett, directionFromNewcastleUponTyne, south-west]
-
A.
directionFromNewcastle
chosen
Indicates the compass direction or relative bearing of one place or object when measured starting from Newcastle as the reference point.
-
B.
directionFromNorwich
Indicates the relative compass direction or bearing of one place or object as measured outward starting from Norwich.
-
C.
distanceFromNewcastle
Indicates the spatial distance between a given entity or location and the city of Newcastle.
-
D.
directionFromNottingham
Indicates the directional relationship of a location or entity as measured outward from Nottingham.
-
E.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4abd9768819091298e4dd995ac96 |
completed | March 31, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.