Triple
T4239553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nissan V platform (first generation) |
E94776
|
entity |
| Predicate | wheelDriveSupported |
P40668
|
FINISHED |
| Object | 2WD |
—
|
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: 2WD | Statement: [Nissan V platform (first generation), wheelDriveSupported, 2WD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelDriveSupported Context triple: [Nissan V platform (first generation), wheelDriveSupported, 2WD]
-
A.
supportsDrivetrainFeature
chosen
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
B.
towingCapability
Indicates the maximum load or object weight that one entity is able to pull or tow.
-
C.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
D.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
E.
drivetrainRole
Indicates the functional role or position an entity has within a drivetrain system (e.g., input, transmission, or output component).
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e77fb5c8190b298818acb68ff63 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.