Triple
T17988421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col du Tourmalet |
E430301
|
entity |
| Predicate | hasClimbingSide |
P54392
|
FINISHED |
| Object | west side from Luz-Saint-Sauveur |
—
|
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: west side from Luz-Saint-Sauveur | Statement: [Col du Tourmalet, hasClimbingSide, west side from Luz-Saint-Sauveur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingSide Context triple: [Col du Tourmalet, hasClimbingSide, west side from Luz-Saint-Sauveur]
-
A.
hasClimbSide
chosen
Indicates that one entity has a particular side or surface that is suitable or designated for climbing.
-
B.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
C.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within another entity.
-
D.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
E.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29d3ad4819096c2600aa2a99f21 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.