Triple
T32425870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pau–Canfranc railway |
E828574
|
entity |
| Predicate | mountainousRoute |
P170931
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pau–Canfranc railway, mountainousRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainousRoute Context triple: [Pau–Canfranc railway, mountainousRoute, true]
-
A.
includesMountainRoutes
chosen
Indicates that the described route, path, or itinerary contains one or more segments that pass through or over mountainous terrain.
-
B.
isMountainRoad
Indicates that a given road is classified as a mountain road, typically traversing or situated within mountainous terrain.
-
C.
glacialRoute
Indicates a path or course shaped, carved, or followed by a glacier as it moves across a landscape.
-
D.
controlledMountainPasses
Indicates that an entity had authority over and could regulate access through specific mountain passes.
-
E.
borderMountainOf
Indicates that a mountain lies along or forms part of the border of a specified region or 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c287740c8190a91da975e50564dc |
completed | May 3, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.