Triple
T31341131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omloop Het Nieuwsblad |
E799307
|
entity |
| Predicate | typicalRaceStyle |
P56420
|
FINISHED |
| Object | aggressive |
—
|
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: aggressive | Statement: [Omloop Het Nieuwsblad, typicalRaceStyle, aggressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRaceStyle Context triple: [Omloop Het Nieuwsblad, typicalRaceStyle, aggressive]
-
A.
styleOfRacing
chosen
Indicates the specific manner or approach in which an entity participates in or performs racing.
-
B.
typicalRaceLengthCategory
Indicates the usual distance range or length classification that a race is most commonly run at.
-
C.
notableRaceStyle
Indicates that an entity is particularly recognized for competing in, specializing in, or being associated with a specific style or category of racing.
-
D.
stageRaceType
Indicates the specific category or format of a multi-stage race within a broader competition or event.
-
E.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:16 p.m.