Triple
T13561510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volvo S60 |
E323918
|
entity |
| Predicate | driveTypeAvailable |
P4169
|
FINISHED |
| Object | FWD |
—
|
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: FWD | Statement: [Volvo S60, driveTypeAvailable, FWD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driveTypeAvailable Context triple: [Volvo S60, driveTypeAvailable, FWD]
-
A.
driveType
chosen
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
B.
driverType
Indicates the category or role of a driver associated with an entity or activity (e.g., primary, backup, commercial, etc.).
-
C.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
-
D.
driveModes
Indicates that an entity (such as a vehicle or device) supports or operates in one or more specific driving or operational modes.
-
E.
supportsMobilityType
Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.