Triple
T4067884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Rollright |
E86369
|
entity |
| Predicate | distanceToChippingNorton |
P53298
|
FINISHED |
| Object | approximately 3 miles north |
—
|
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: approximately 3 miles north | Statement: [Great Rollright, distanceToChippingNorton, approximately 3 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChippingNorton Context triple: [Great Rollright, distanceToChippingNorton, approximately 3 miles north]
-
A.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
B.
isCloseTo
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
C.
distanceToBingham
Indicates the measured or calculated distance between a given entity and the location named Bingham.
-
D.
distanceFromMina
Indicates the spatial distance measured between Mina and another specified entity or location.
-
E.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf73a1c81909f1741f4ecf55f98 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa5c52648190b001027f4dba75cb |
completed | March 9, 2026, 4:50 p.m. |
Created at: March 9, 2026, 3:38 p.m.