Triple
T3487948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorentz force |
E73654
|
entity |
| Predicate | magneticPartPerpendicularTo |
P2055
|
FINISHED |
| Object | velocity |
—
|
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: velocity | Statement: [Lorentz force, magneticPartPerpendicularTo, velocity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magneticPartPerpendicularTo Context triple: [Lorentz force, magneticPartPerpendicularTo, velocity]
-
A.
perpendicularTo
chosen
Indicates that one entity is oriented at a right angle (90 degrees) to another entity.
-
B.
magneticField
Indicates the presence, strength, or configuration of a magnetic field associated with an entity or region.
-
C.
magneticFieldCharacteristic
Indicates a relationship where a magnetic field is associated with or exhibits a specific characteristic or property.
-
D.
hasMagneticMoment
Indicates that an entity possesses a magnetic moment, characterizing the strength and orientation of its magnetism.
-
E.
magneticFieldStrength
Indicates the intensity or magnitude of a magnetic field associated with an entity or at a specific location.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb9193688190aa0cbf87a7b99446 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.