Triple
T17947945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fleming’s right-hand rule |
E448753
|
entity |
| Predicate | leftHandRuleUsedFor |
P129845
|
FINISHED |
| Object | electric motors |
—
|
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: electric motors | Statement: [Fleming’s right-hand rule, leftHandRuleUsedFor, electric motors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftHandRuleUsedFor Context triple: [Fleming’s right-hand rule, leftHandRuleUsedFor, electric motors]
-
A.
rightHandRuleUsage
Indicates the use of the right-hand rule to determine the direction or orientation of a vector or rotational effect resulting from another vector or motion.
-
B.
carriedInRightOrLeftHand
Indicates that an entity is being held and transported either in the right hand or in the left hand of an agent.
-
C.
handedness
Indicates the preference or dominance of one hand over the other in performing actions or tasks.
-
D.
rightHandedComponent
Indicates that one entity functions as the right-handed component or counterpart within a paired or bilateral relationship to another entity.
-
E.
ambidextrousUse
Indicates the ability to use both the left and right hands with equal skill or effectiveness for a given action or task.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afa9cb2481908c95f8c430dcc0aa |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.