Triple
T36115408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GR-Four |
E1044603
|
entity |
| Predicate | vehicleLayoutCompatibility |
P185034
|
FINISHED |
| Object | front-engine layout |
—
|
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: front-engine layout | Statement: [GR-Four, vehicleLayoutCompatibility, front-engine layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleLayoutCompatibility Context triple: [GR-Four, vehicleLayoutCompatibility, front-engine layout]
-
A.
vehicleLayout
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
B.
busCompatibility
Indicates that two hardware or software components can operate together correctly over the same communication bus or interface.
-
C.
vehicleDeckCapacity
Indicates the maximum number or volume of vehicles that a deck is designed to accommodate.
-
D.
supportsChassisType
Indicates that one entity is compatible with and can be used to support or accommodate a specified chassis type.
-
E.
usesCarWidth
Indicates that one entity determines, measures, or constrains something based on the width of a car.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:08 p.m.