Triple
T3768429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tour of Qatar |
E82736
|
entity |
| Predicate | notableRiderType |
P51007
|
FINISHED |
| Object | cobble classics specialists |
—
|
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: cobble classics specialists | Statement: [Tour of Qatar, notableRiderType, cobble classics specialists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRiderType Context triple: [Tour of Qatar, notableRiderType, cobble classics specialists]
-
A.
notableRacingVariant
Indicates that one entity is a particularly recognized or distinguished racing-specific version or trim of another entity.
-
B.
winnerRider
Indicates that a rider is the one who won a particular race or competition.
-
C.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
D.
notableParticipant
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
E.
primaryRiders
Indicates that the referenced entities are the main or principal riders associated with a particular vehicle, trip, or ride-related event.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2d4b848190bf63fb3ed5d3b2d9 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:35 p.m.