Triple
T25820108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cresta de los Portillones |
E650376
|
entity |
| Predicate | onNormalRouteTo |
P158225
|
FINISHED |
| Object | Pico de Aneto |
—
|
NE NERFINISHED |
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: Pico de Aneto | Statement: [Cresta de los Portillones, onNormalRouteTo, Pico de Aneto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onNormalRouteTo Context triple: [Cresta de los Portillones, onNormalRouteTo, Pico de Aneto]
-
A.
onStandardRouteOf
chosen
Indicates that something lies along or follows the usual, predefined, or officially designated route of another entity.
-
B.
nextRoute
Indicates that one route directly follows another in a defined sequence or ordering of routes.
-
C.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
D.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
E.
mayRouteTo
Indicates that one entity is permitted or able to direct, forward, or transfer something (such as data, traffic, or requests) to another entity.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601909ea481909674a1438dede725 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:29 a.m.