Triple
T4593844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Taunus V4 engine |
E103560
|
entity |
| Predicate | boreSpacing |
P58187
|
FINISHED |
| Object | common with Ford Cologne V6 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: common with Ford Cologne V6 engine | Statement: [Ford Taunus V4 engine, boreSpacing, common with Ford Cologne V6 engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boreSpacing Context triple: [Ford Taunus V4 engine, boreSpacing, common with Ford Cologne V6 engine]
-
A.
hasBoreType
Indicates that an entity is characterized by or associated with a specific type of bore (e.g., cylindrical, tapered, rifled).
-
B.
cylinderBore
Indicates the diameter of the cylindrical chamber (bore) in which a piston or similar component moves.
-
C.
bore
Indicates that one entity caused another entity to feel uninterested, tired, or lacking in engagement.
-
D.
gapBetween
Indicates the spatial or temporal distance or separation that exists between two entities.
-
E.
shaftCount
Indicates the number of shafts associated with or contained in an object or system.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd593e115081909b11149e02fe4ef3 |
completed | March 20, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.