Triple
T27642945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garmin-Slipstream |
E696632
|
entity |
| Predicate | notableResultType |
P111111
|
FINISHED |
| Object | Grand Tour stage wins |
—
|
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: Grand Tour stage wins | Statement: [Garmin-Slipstream, notableResultType, Grand Tour stage wins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableResultType Context triple: [Garmin-Slipstream, notableResultType, Grand Tour stage wins]
-
A.
notableOutcomeType
Indicates that a relationship exists where an outcome is characterized as being of a particular notable or significant type.
-
B.
notableResultDriver
Indicates that an entity is a primary or especially influential factor contributing to a notable result or outcome for another entity.
-
C.
notableWinType
chosen
Indicates that the relationship specifies the particular category or type of a notable victory associated with an entity.
-
D.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
E.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: April 27, 2026, 2:27 p.m.