Triple
T32214539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Dibona |
E822891
|
entity |
| Predicate | approachTimeFromValley |
P20400
|
FINISHED |
| Object | about 3 hours to Refuge du Soreiller |
—
|
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 3 hours to Refuge du Soreiller | Statement: [La Dibona, approachTimeFromValley, about 3 hours to Refuge du Soreiller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachTimeFromValley Context triple: [La Dibona, approachTimeFromValley, about 3 hours to Refuge du Soreiller]
-
A.
startsFromValley
Indicates that an entity begins its path, route, or progression at a valley location.
-
B.
approximateAscentTimeFromRefuge
chosen
Indicates the estimated amount of time required to ascend from a specified refuge to a target point or destination.
-
C.
hasApproachTime
Indicates that an entity is associated with a specific time at which it approaches or comes near another entity or location.
-
D.
timeToReachTown
Indicates the amount of time required for an entity to travel to and arrive at a specified town.
-
E.
traversesValley
Indicates that an entity moves through or across a valley, passing from one side or area to another.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 1, 2026, 12:37 a.m.