Triple
T35390763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col du Télégraphe |
E1022929
|
entity |
| Predicate | approximateClimbLengthFromSaintMichel |
P199774
|
FINISHED |
| Object | about 12 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 12 km | Statement: [Col du Télégraphe, approximateClimbLengthFromSaintMichel, about 12 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateClimbLengthFromSaintMichel Context triple: [Col du Télégraphe, approximateClimbLengthFromSaintMichel, about 12 km]
-
A.
climbFromSaintÉtienneDeTinéeLength
Indicates the length or distance of a climb that starts from Saint-Étienne-de-Tinée.
-
B.
distanceToSaint-Étienne
Indicates the measured or specified distance between a given entity and the location Saint-Étienne.
-
C.
distanceToLePuy-en-Velay
Indicates the spatial distance between a given entity and the location of Le Puy-en-Velay.
-
D.
distanceToPauKmApprox
Indicates an approximate distance, measured in kilometers, from an entity to the location Pau.
-
E.
elevationRelativeToParis
Indicates the relative elevation difference between a given location and Paris, specifying how much higher or lower it is in altitude.
- F. None of above. chosen
Provenance (4 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
| PDg | Predicate description generation | batch_69ff56edc4d081908f1d263e05cbd512 |
completed | May 9, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.