Triple
T17947950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fleming’s right-hand rule |
E448753
|
entity |
| Predicate | firstFingerAxis |
P32356
|
FINISHED |
| Object | magnetic field axis |
—
|
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: magnetic field axis | Statement: [Fleming’s right-hand rule, firstFingerAxis, magnetic field axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFingerAxis Context triple: [Fleming’s right-hand rule, firstFingerAxis, magnetic field axis]
-
A.
firstLeg
Indicates that one entity represents the initial segment or starting portion of a multi-part journey, sequence, or process involving another entity.
-
B.
firstMovementKey
Indicates the musical key in which the first movement of a multi-movement work is composed.
-
C.
axePosition
Indicates the spatial location or orientation of an axe relative to a reference point or object.
-
D.
usesAxis
chosen
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
-
E.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
- 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_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. |
Created at: April 10, 2026, 10:21 a.m.