Triple
T7162759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attleborough |
E166985
|
entity |
| Predicate | distanceFromThetford |
P75219
|
FINISHED |
| Object | about 14 miles northeast |
—
|
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: about 14 miles northeast | Statement: [Attleborough, distanceFromThetford, about 14 miles northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromThetford Context triple: [Attleborough, distanceFromThetford, about 14 miles northeast]
-
A.
distanceToTelford
Indicates the spatial distance between a given entity and the location of Telford.
-
B.
distanceToSwaffham
Indicates the spatial distance between a given entity and the location Swaffham.
-
C.
distanceToFakenham
Indicates the spatial distance between a given entity and the location Fakenham.
-
D.
distanceToWymondham
Indicates the spatial distance between a given entity or location and Wymondham.
-
E.
distanceToChelmsford
Indicates the spatial distance between a given entity’s location and the location of Chelmsford.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e82feee481908fa180ea8c9924fa |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:47 p.m.