Triple
T29526745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford flathead V8 |
E749088
|
entity |
| Predicate | boreLayout |
P52917
|
FINISHED |
| Object | siamesed cylinders |
—
|
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: siamesed cylinders | Statement: [Ford flathead V8, boreLayout, siamesed cylinders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boreLayout Context triple: [Ford flathead V8, boreLayout, siamesed cylinders]
-
A.
boreSpacing
Indicates the center-to-center distance between adjacent bores or holes in a component or assembly.
-
B.
bore
Indicates that one entity caused another entity to feel uninterested, tired, or lacking in engagement.
-
C.
hasBoreType
chosen
Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
-
D.
boreStrokeDesign
Indicates that an engine’s bore and stroke configuration is designed or specified in a particular way.
-
E.
hasBore
Indicates that one object possesses or is characterized by a specific bore, such as the internal diameter of a tube, pipe, or barrel.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c9d5df48190ad10afb467a9c7a6 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:47 p.m.