Triple
T32882204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigginton, Hertfordshire |
E841093
|
entity |
| Predicate | distanceToTring |
P3387
|
FINISHED |
| Object | approximately 2 miles south |
—
|
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 2 miles south | Statement: [Wigginton, Hertfordshire, distanceToTring, approximately 2 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTring Context triple: [Wigginton, Hertfordshire, distanceToTring, approximately 2 miles south]
-
A.
distanceToTerminal
Indicates the measured or calculated distance from a given entity or location to a specified terminal point or facility.
-
B.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
C.
distanceFromTerminus
chosen
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
D.
hopDistance
Indicates the number of intermediate steps or "hops" required to traverse from one entity to another within a network or graph.
-
E.
distanceProvidedBy
Indicates that a specific distance value is supplied or made available by a particular source or provider.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:18 a.m.