Triple
T4549454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfa Romeo Giulia |
E110125
|
entity |
| Predicate | driveAssistFeature |
P57935
|
FINISHED |
| Object | adaptive cruise control |
—
|
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: adaptive cruise control | Statement: [Alfa Romeo Giulia, driveAssistFeature, adaptive cruise control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driveAssistFeature Context triple: [Alfa Romeo Giulia, driveAssistFeature, adaptive cruise control]
-
A.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
B.
drives
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
-
C.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
D.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
E.
driveResult
Indicates the outcome or consequence produced by a driving action or driving-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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f3f8348190868e274ac4df87ce |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:05 p.m.