Triple
T12443464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Luis Peak |
E297334
|
entity |
| Predicate | hasEasiestRouteClass |
P1322
|
FINISHED |
| Object | Class 1 |
—
|
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: Class 1 | Statement: [San Luis Peak, hasEasiestRouteClass, Class 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEasiestRouteClass Context triple: [San Luis Peak, hasEasiestRouteClass, Class 1]
-
A.
hasEasiestRoute
chosen
Indicates that one entity provides or represents the simplest or least difficult route or path to reach another entity or destination.
-
B.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
C.
hasNotableRoute
Indicates that an entity (such as a transportation service or pathway) includes or is associated with a route that is considered significant, well-known, or otherwise noteworthy.
-
D.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
E.
hasMajorRouteType
Indicates that an entity is associated with a primary classification of transportation route (such as highway, rail line, or other major route type).
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95151e7348190a1d4953a8b416a13 |
completed | April 10, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69d94d3c27a08190a0237200203e476d |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.