Triple
T28651908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modular Transverse Matrix |
E725222
|
entity |
| Predicate | designedForEngineLayout |
P9494
|
FINISHED |
| Object | front‑engined vehicles |
—
|
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‑engined vehicles | Statement: [Modular Transverse Matrix, designedForEngineLayout, front‑engined vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForEngineLayout Context triple: [Modular Transverse Matrix, designedForEngineLayout, front‑engined vehicles]
-
A.
boreStrokeDesign
Indicates that an engine’s bore and stroke configuration is designed or specified in a particular way.
-
B.
engineeredForLabel
Indicates that something has been specifically designed, adapted, or optimized to serve, support, or be used for the referenced label or purpose.
-
C.
propulsionLayout
Indicates how propulsion components are arranged or configured relative to each other within a system.
-
D.
enginePlacement
Indicates the spatial or structural position where an engine is located or mounted relative to another object or system.
-
E.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 4:52 a.m.