Triple
T9044642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EcoTec3 V8 |
E216722
|
entity |
| Predicate | boreCenterDistance |
P58187
|
FINISHED |
| Object | 4.4 inch GM small-block standard |
—
|
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: 4.4 inch GM small-block standard | Statement: [EcoTec3 V8, boreCenterDistance, 4.4 inch GM small-block standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boreCenterDistance Context triple: [EcoTec3 V8, boreCenterDistance, 4.4 inch GM small-block standard]
-
A.
boreSpacing
chosen
Indicates the center-to-center distance between adjacent bores or holes in a component or assembly.
-
B.
cylinderBore
Indicates the diameter of the cylindrical chamber (bore) in which a piston or similar component moves.
-
C.
shaftDiameterAtBase
Indicates the diameter measurement of a shaft specifically at its base portion.
-
D.
hasBoreType
Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
-
E.
shaftDiameterAtTop
Indicates the diameter measurement of a shaft specifically at its top end or uppermost section.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b137cec8190bd1b812c10d9542a |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.