Triple
T24903897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIA World Rally-Raid Championship |
E623651
|
entity |
| Predicate | involvesVehicleType |
P1776
|
FINISHED |
| Object | side-by-side vehicles |
—
|
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: side-by-side vehicles | Statement: [FIA World Rally-Raid Championship, involvesVehicleType, side-by-side vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesVehicleType Context triple: [FIA World Rally-Raid Championship, involvesVehicleType, side-by-side vehicles]
-
A.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
B.
vehicleFor
Indicates that one entity serves as the means of transportation or conveyance for another entity.
-
C.
appliedToVehicleType
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
-
D.
utilityInvolved
Indicates that a utility service or provider is involved in, associated with, or plays a role in the referenced situation or relationship.
-
E.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 5:27 a.m.