Triple
T22524852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Dinamos cliffs |
E556871
|
entity |
| Predicate | routeVariety |
P6300
|
FINISHED |
| Object | single-pitch routes |
—
|
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: single-pitch routes | Statement: [Los Dinamos cliffs, routeVariety, single-pitch routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeVariety Context triple: [Los Dinamos cliffs, routeVariety, single-pitch routes]
-
A.
routeVariesBy
Indicates that the characteristics or details of a route change depending on certain conditions, parameters, or contexts.
-
B.
routeCategory
chosen
Indicates the classification or type assigned to a route within a transportation or path network.
-
C.
routeChoiceIn
Indicates that a particular route is selected or used within a given route choice or decision context.
-
D.
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.
-
E.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e356b4081909d1ce911bd35fe68 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:51 p.m.