Triple
T7531528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Russian Grand Prix |
E178033
|
entity |
| Predicate | raceDistanceKm |
P33049
|
FINISHED |
| Object | 309.745 |
—
|
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: 309.745 | Statement: [2014 Russian Grand Prix, raceDistanceKm, 309.745]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceDistanceKm Context triple: [2014 Russian Grand Prix, raceDistanceKm, 309.745]
-
A.
lengthInKm
chosen
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
B.
raceDistanceType
Indicates the specific type or category of distance over which a race is conducted.
-
C.
raceDistanceApprox
Indicates that the distance of a race is approximately equal to a specified value, allowing for some margin of error rather than requiring an exact match.
-
D.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
E.
range_km
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8217b1c8190b3db453cee0fc4fd |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.