Triple
T5995215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loches |
E133450
|
entity |
| Predicate | distanceFromTours |
P7750
|
FINISHED |
| Object | about 40 km southeast |
—
|
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 40 km southeast | Statement: [Loches, distanceFromTours, about 40 km southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTours Context triple: [Loches, distanceFromTours, about 40 km southeast]
-
A.
hasApproximateDrivingDistanceFrom
Indicates that one entity is located at an estimated or approximate driving distance from another entity, typically measured along road routes rather than as a precise or exact value.
-
B.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
C.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
D.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
E.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e943dcc8190a09817e8ef0e4188 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.