Triple
T3737861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holden Calais |
E79627
|
entity |
| Predicate | typicalDriveLayout |
P4169
|
FINISHED |
| Object | rear-wheel drive |
—
|
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: rear-wheel drive | Statement: [Holden Calais, typicalDriveLayout, rear-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDriveLayout Context triple: [Holden Calais, typicalDriveLayout, rear-wheel drive]
-
A.
driveType
chosen
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
B.
driveLayoutSupported
Indicates that a particular drive layout or configuration is compatible with and can be correctly handled by a given system or component.
-
C.
vehicleLayout
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
D.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
E.
typicalSeat
Indicates the usual or standard seating position or location associated with an entity in a given context.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3e9248819098d481fe29e1c628 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.