Triple
T34131655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mur de Huy |
E875440
|
entity |
| Predicate | isKeyClimbOf |
P178430
|
FINISHED |
| Object | La Flèche Wallonne |
—
|
NE NERFINISHED |
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: La Flèche Wallonne | Statement: [Mur de Huy, isKeyClimbOf, La Flèche Wallonne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyClimbOf Context triple: [Mur de Huy, isKeyClimbOf, La Flèche Wallonne]
-
A.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
B.
isClimbedToReach
Indicates that an entity ascends or climbs another entity in order to reach a target or destination.
-
C.
isCobbledClimbOf
Indicates that one location or route is a cobblestone-paved climbing segment that belongs to or forms part of another, larger route or course.
-
D.
hasClimbFrom
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.
-
E.
hasNearbyClimb
Indicates that one location or entity is situated close to a climbable feature or climbing route.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:53 a.m.