Triple
T38687051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 326 cu in Pontiac V8 |
E949145
|
entity |
| Predicate | mountingLayout |
P192349
|
FINISHED |
| Object | longitudinal front-engine |
—
|
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: longitudinal front-engine | Statement: [326 cu in Pontiac V8, mountingLayout, longitudinal front-engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountingLayout Context triple: [326 cu in Pontiac V8, mountingLayout, longitudinal front-engine]
-
A.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
B.
trainMounting
Indicates a relationship where an entity is boarding or getting onto a train.
-
C.
mountingInterface
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
-
D.
mountType
Indicates the manner or configuration in which one object is mounted or attached to another.
-
E.
guardMounting
Indicates the action of assigning or taking up a position for guard duty, typically as part of a scheduled security or watch rotation.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: May 3, 2026, 4:33 p.m.