Triple
T34131654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mur de Huy |
E875440
|
entity |
| Predicate | isFinishOf |
P113802
|
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, isFinishOf, La Flèche Wallonne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFinishOf Context triple: [Mur de Huy, isFinishOf, La Flèche Wallonne]
-
A.
isFinishLineOf
chosen
Indicates that something serves as the finish line or endpoint for a particular event, race, or process.
-
B.
isSignatureFinishOf
Indicates that something serves as the distinctive or characteristic finishing element associated with a particular entity (such as a person, product, or work).
-
C.
isOfficialFinishFor
Indicates that one event, result, or record serves as the formally recognized completion point for another process, activity, or competition.
-
D.
concludesIn
Indicates that an event, process, or action ends or reaches its final state within a specified time, place, or context.
-
E.
isLikelyToEndAs
Indicates that one entity is predicted or expected to ultimately result in, conclude as, or transform into another entity or outcome.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.