Triple
T11506979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont du Chat |
E272809
|
entity |
| Predicate | hasRoadClimb |
P52151
|
FINISHED |
| Object | climb from Le Bourget-du-Lac |
—
|
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: climb from Le Bourget-du-Lac | Statement: [Mont du Chat, hasRoadClimb, climb from Le Bourget-du-Lac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadClimb Context triple: [Mont du Chat, hasRoadClimb, climb from Le Bourget-du-Lac]
-
A.
hasClimbFrom
chosen
Indicates a relationship where one location or object serves as the starting point from which a climb or ascent to another location or object begins.
-
B.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
C.
hasStaircaseToSummit
Indicates that there exists a staircase providing a direct route or access from a lower point to the summit of something.
-
D.
hasIncline
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
-
E.
hasClimbsCount
Indicates that an entity is associated with a specific number of climbs it has completed or is credited with.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db43a648190be859bec2fe9f43b |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.