Triple
T3487950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorentz force |
E73654
|
entity |
| Predicate | electricPartParallelTo |
P49065
|
FINISHED |
| Object | electric field |
—
|
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 field | Statement: [Lorentz force, electricPartParallelTo, electric field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricPartParallelTo Context triple: [Lorentz force, electricPartParallelTo, electric field]
-
A.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
B.
structureParallels
Indicates that the structural organization or arrangement of one entity closely corresponds to or mirrors that of another.
-
C.
electricalPolarity
Indicates that there is a relationship specifying the direction or type of electrical charge or potential difference associated with an entity or connection.
-
D.
electricalSystem
Indicates that one entity functions as, is part of, or is directly related to the electrical system of another entity.
-
E.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
- 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_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. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:18 p.m.