Triple
T18638745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Don Engine |
E455623
|
entity |
| Predicate | mechanicalFunction |
P132490
|
FINISHED |
| Object | reciprocating 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: reciprocating engine | Statement: [River Don Engine, mechanicalFunction, reciprocating engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicalFunction Context triple: [River Don Engine, mechanicalFunction, reciprocating engine]
-
A.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
B.
mechanismExample
Indicates that one entity serves as an illustrative example of the mechanism or process by which another entity operates or produces an effect.
-
C.
mechanicalDesign
Indicates that one entity is responsible for or associated with the mechanical design or engineering configuration of another entity.
-
D.
featuresMechanic
Indicates that something includes or incorporates a particular mechanic as part of its design or functionality.
-
E.
isMechanicalOrElectronic
Indicates that something operates using mechanical components, electronic components, or a combination of both.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fcac2d48190a15ce8cc8e175198 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:47 a.m.