Triple
T32730112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leclerc (licensed derivative) |
E836924
|
entity |
| Predicate | hasChassisLayout |
P187575
|
FINISHED |
| Object | front-mounted driver position |
—
|
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-mounted driver position | Statement: [Leclerc (licensed derivative), hasChassisLayout, front-mounted driver position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChassisLayout Context triple: [Leclerc (licensed derivative), hasChassisLayout, front-mounted driver position]
-
A.
hasChassisType
Indicates that an entity is associated with or equipped with a specific type of chassis.
-
B.
intendedVehicleLayout
chosen
Indicates the planned or designed seating or interior configuration that a vehicle is meant to have.
-
C.
hasChassisFamily
Indicates that an entity belongs to or is associated with a particular chassis family or chassis type group.
-
D.
supportsChassisType
Indicates that one entity is compatible with and can be used to support or accommodate a specified chassis type.
-
E.
vehicleLayoutCompatibility
Indicates that two vehicle-related components or systems are suitable to be arranged or integrated together within a given vehicle layout.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 1, 2026, 1:11 a.m.