Triple
T37268624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springer Softail |
E924452
|
entity |
| Predicate | hasEngineStrokeCycle |
P150855
|
FINISHED |
| Object | 4-stroke |
—
|
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-stroke | Statement: [Springer Softail, hasEngineStrokeCycle, 4-stroke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineStrokeCycle Context triple: [Springer Softail, hasEngineStrokeCycle, 4-stroke]
-
A.
usesEngineCycle
Indicates that one entity operates or functions by employing the engine cycle specified by another entity.
-
B.
pistonStrokeCycle
chosen
Indicates the cyclical movement pattern of a piston as it completes its sequence of strokes within an engine’s operating cycle.
-
C.
hasCrankshaftPosition
Indicates that an entity has or is associated with a specific crankshaft position in a mechanical or engine context.
-
D.
hasFuelCycleCapability
Indicates that an entity possesses the technical and operational ability to carry out one or more stages of the nuclear fuel cycle (such as fuel production, use, or reprocessing).
-
E.
hasEngineProgram
Indicates that an entity is associated with or participates in a specific engine-related program.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:15 p.m.