Triple
T15670682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardennes classics |
E377302
|
entity |
| Predicate | decisiveFeature |
P119687
|
FINISHED |
| Object | repeated short climbs |
—
|
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: repeated short climbs | Statement: [Ardennes classics, decisiveFeature, repeated short climbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveFeature Context triple: [Ardennes classics, decisiveFeature, repeated short climbs]
-
A.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
B.
decisive
Indicates that one entity makes a conclusive choice or determination that resolves a situation or outcome between entities.
-
C.
decisionMakingTool
Indicates that an entity functions as a tool or system used to support, structure, or carry out decision-making processes for another entity.
-
D.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
E.
deciderOf
Indicates that one entity is the one who makes decisions or choices regarding another entity or situation.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f1254508190a77a16b7bfd299ad |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:16 a.m.