Triple
T18828066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis Asbury |
E460443
|
entity |
| Predicate | estimatedMilesTraveled |
P26813
|
FINISHED |
| Object | 270000 |
—
|
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: 270000 | Statement: [Francis Asbury, estimatedMilesTraveled, 270000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedMilesTraveled Context triple: [Francis Asbury, estimatedMilesTraveled, 270000]
-
A.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
B.
approximateLengthInMiles
chosen
Indicates the estimated distance or extent of something measured in miles.
-
C.
vehicleRestrictionMile
Indicates a restriction or limitation that applies to vehicles at a specific mile point or mile marker along a route.
-
D.
mileageAccrual
Indicates the accumulation or earning of mileage (such as distance-based points or credits) as a result of certain actions or usage.
-
E.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99554848190933dd2810f5c810f |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.