Triple
T2097245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henley-on-Thames |
E37009
|
entity |
| Predicate | distanceFromReading |
P35932
|
FINISHED |
| Object | about 9 miles northeast of Reading |
—
|
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 9 miles northeast of Reading | Statement: [Henley-on-Thames, distanceFromReading, about 9 miles northeast of Reading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromReading Context triple: [Henley-on-Thames, distanceFromReading, about 9 miles northeast of Reading]
-
A.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
-
B.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
C.
distanceToBingham
Indicates the measured or calculated distance between a given entity and the location named Bingham.
-
D.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
E.
distanceFromLeeds
Indicates the spatial distance between a given entity and the location of Leeds.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba9cb84481909fe0a66c020b8864 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abba2e65b48190bb19cfc4b0f8c462 |
completed | March 7, 2026, 5:39 a.m. |
Created at: March 4, 2026, 7:43 p.m.