Triple
T25053368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sloan, Nevada |
E627444
|
entity |
| Predicate | nearestInterstateExit |
P158391
|
FINISHED |
| Object | Sloan exit on Interstate 15 |
—
|
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: Sloan exit on Interstate 15 | Statement: [Sloan, Nevada, nearestInterstateExit, Sloan exit on Interstate 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestInterstateExit Context triple: [Sloan, Nevada, nearestInterstateExit, Sloan exit on Interstate 15]
-
A.
nearestInterstateHighway
Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
-
B.
nearestTurnpikeInterchange
Indicates that one location is the closest turnpike interchange to another specified location.
-
C.
nearbyHighwayMilepost
Indicates that one entity is located close to a specific highway milepost associated with another entity.
-
D.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
-
E.
nearestMotorway
Indicates that one entity is the motorway that is geographically closest to the other entity.
- F. None of above. chosen
Provenance (4 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 18, 2026, 6:09 a.m.