Triple
T25431906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Ridge (Integral) |
E637279
|
entity |
| Predicate | routeStyle |
P159122
|
FINISHED |
| Object | ridge traverse |
—
|
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: ridge traverse | Statement: [South Ridge (Integral), routeStyle, ridge traverse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeStyle Context triple: [South Ridge (Integral), routeStyle, ridge traverse]
-
A.
routeSymbolShape
Indicates the specific geometric form or outline used to depict a route’s symbol in a visual or cartographic representation.
-
B.
routeSymbol
Indicates that a particular symbol or code is used to represent or identify a specific route.
-
C.
routeSetting
Indicates that one entity configures or defines the path or course to be followed by another entity (such as a vehicle, signal, or data flow).
-
D.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
-
E.
routesFrom
Indicates that something (such as a path, connection, or communication) originates at one entity and is directed or carried from that source entity toward another.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6db636c8190880178c72ed6d38a |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 1:58 p.m.