Triple
T19165802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajo Mountain Drive |
E469176
|
entity |
| Predicate | timeToDrive |
P89543
|
FINISHED |
| Object | approximately 2 to 3 hours with stops |
—
|
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 to 3 hours with stops | Statement: [Ajo Mountain Drive, timeToDrive, approximately 2 to 3 hours with stops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToDrive Context triple: [Ajo Mountain Drive, timeToDrive, approximately 2 to 3 hours with stops]
-
A.
approximateDrivingTime
chosen
Indicates the estimated amount of time it takes to drive from one location to another under typical conditions.
-
B.
drivingTimeFromNewYorkCity
Indicates the amount of time it takes to drive from New York City to a specified location.
-
C.
approximateDrivingTimeFromLAnse
Indicates the estimated amount of time it takes to drive from L'Anse to another specified location.
-
D.
drivingTimeFromLosAngeles
Indicates the amount of time it takes to drive from Los Angeles to a specified location.
-
E.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f15ee064819087f9fd822236298f |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.