Triple
T7972815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE 7FDL16 |
E185367
|
entity |
| Predicate | displacementPerCylinder |
P80098
|
FINISHED |
| Object | approximately 567 cubic inches |
—
|
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: approximately 567 cubic inches | Statement: [GE 7FDL16, displacementPerCylinder, approximately 567 cubic inches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementPerCylinder Context triple: [GE 7FDL16, displacementPerCylinder, approximately 567 cubic inches]
-
A.
engineDisplacement
Indicates the total volume swept by all the pistons inside an engine’s cylinders during one complete cycle.
-
B.
pistonStroke
Indicates the distance or movement range that a piston travels within a cylinder during one complete stroke.
-
C.
numberOfCylinders
Indicates the count of engine cylinders associated with an entity.
-
D.
valvesPerCylinder
Indicates the number of valves associated with each individual cylinder in an engine.
-
E.
availableEngineDisplacement
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd580dc819084be5b7963b6029c |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:13 p.m.