Triple
T34331383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Meteor |
E881015
|
entity |
| Predicate | crankshaftDirection |
P25585
|
FINISHED |
| Object | clockwise (viewed from rear) |
—
|
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: clockwise (viewed from rear) | Statement: [Rolls-Royce Meteor, crankshaftDirection, clockwise (viewed from rear)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crankshaftDirection Context triple: [Rolls-Royce Meteor, crankshaftDirection, clockwise (viewed from rear)]
-
A.
crankshaftType
Indicates the specific design or configuration of a crankshaft that an entity uses or is associated with.
-
B.
shaftOrientation
chosen
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
-
C.
camshaftType
Indicates the specific design or configuration of camshaft associated with an engine or mechanical system.
-
D.
shaftArrangement
Indicates how one or more shafts are positioned, oriented, or configured relative to each other within a mechanical or structural system.
-
E.
camshaftConfiguration
Indicates how the camshafts are arranged or configured within an engine’s valve train system.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.