Triple
T13426432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally Turkey |
E313492
|
entity |
| Predicate | typicalRallyFormat |
P2673
|
FINISHED |
| Object | special stages against the clock |
—
|
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: special stages against the clock | Statement: [Rally Turkey, typicalRallyFormat, special stages against the clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRallyFormat Context triple: [Rally Turkey, typicalRallyFormat, special stages against the clock]
-
A.
typicalRaceWeekendStructure
Indicates the usual sequence and organization of sessions and activities that make up a standard race weekend.
-
B.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
-
C.
typicalRaceDistanceLaps
Indicates the usual number of laps that constitute the standard race distance for a given racing event or category.
-
D.
styleOfRacing
Indicates the specific manner or approach in which an entity participates in or performs racing.
-
E.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed1f9208190bf5ef5b8a7ded376 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.