Triple
T28273099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty-mule teams |
E712907
|
entity |
| Predicate | distanceTraveledPerTrip |
P16230
|
FINISHED |
| Object | approximately 165 miles |
—
|
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 165 miles | Statement: [Twenty-mule teams, distanceTraveledPerTrip, approximately 165 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceTraveledPerTrip Context triple: [Twenty-mule teams, distanceTraveledPerTrip, approximately 165 miles]
-
A.
distanceTraveled
chosen
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
B.
numberOfDailyRoundTrips
Indicates the total count of round-trip journeys performed per day in the described context.
-
C.
distancePerLeg
Indicates the distance covered in a single leg or segment of a multi-part journey or route.
-
D.
scheduledDistanceMi
Indicates the planned or expected distance in miles associated with a scheduled event or activity.
-
E.
traveledFor
Indicates that an entity moved or journeyed to a place or event for a specific purpose, reason, or activity.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
Created at: April 27, 2026, 11:18 p.m.