Triple
T29033211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rimac C_Two |
E737783
|
entity |
| Predicate | autonomousDrivingCapability |
P57273
|
FINISHED |
| Object | high-level driver assistance systems |
—
|
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: high-level driver assistance systems | Statement: [Rimac C_Two, autonomousDrivingCapability, high-level driver assistance systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomousDrivingCapability Context triple: [Rimac C_Two, autonomousDrivingCapability, high-level driver assistance systems]
-
A.
driveAssistFeature
Indicates that one entity provides an assistance feature that helps another entity perform driving-related tasks.
-
B.
isDriverless
Indicates that something operates or moves without a human driver controlling it.
-
C.
hasDriverAssistance
chosen
Indicates that an entity is equipped with or supports driver assistance features or systems.
-
D.
canDrive
Indicates that one entity has the ability or permission to operate a vehicle or drive another entity.
-
E.
vehicleFunction
Indicates the functional role or primary purpose that a vehicle is designed or used to perform.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603acd608190b7e0ed75d26b6799 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:56 a.m.