Triple
T16302900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wankel rotary engine |
E395833
|
entity |
| Predicate | hasRotorShape |
P89012
|
FINISHED |
| Object | Reuleaux triangle-like |
—
|
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: Reuleaux triangle-like | Statement: [Wankel rotary engine, hasRotorShape, Reuleaux triangle-like]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRotorShape Context triple: [Wankel rotary engine, hasRotorShape, Reuleaux triangle-like]
-
A.
rotorType
chosen
Indicates the specific kind or category of rotor associated with an entity.
-
B.
rotorConfiguration
Indicates the specific arrangement and setup of rotors within a rotor-based system or mechanism.
-
C.
isRotational
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
-
D.
hasDistinctiveShape
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
E.
hasRotation
Indicates that one entity is rotated with respect to another, or possesses a specific rotational orientation or motion.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e3404288190a7106d62c15c3193 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.