Triple
T38353385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col d’Aubisque |
E1046256
|
entity |
| Predicate | climbLengthFromArgelèsGazostViaSoulor |
P185059
|
FINISHED |
| Object | about 30 km |
—
|
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: about 30 km | Statement: [Col d’Aubisque, climbLengthFromArgelèsGazostViaSoulor, about 30 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbLengthFromArgelèsGazostViaSoulor Context triple: [Col d’Aubisque, climbLengthFromArgelèsGazostViaSoulor, about 30 km]
-
A.
lengthOfClimbFromArgelèsGazostViaSoulor
chosen
Indicates the total distance or elevation gain involved in climbing from Argelès-Gazost to a specified point via the Col du Soulor route.
-
B.
averageGradientFromArgelèsGazostViaSoulor
Indicates the average gradient of a route that starts from Argelès-Gazost and passes via the Soulor.
-
C.
climbFromSaintÉtienneDeTinéeLength
Indicates the length or distance of a climb that starts from Saint-Étienne-de-Tinée.
-
D.
climbLength
Indicates the total distance or vertical extent covered by a climbing route or ascent.
-
E.
distanceToPyrenees
Indicates the spatial distance between a given location or entity and the Pyrenees.
- 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.