Triple
T31898246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coulomb potential |
E814348
|
entity |
| Predicate | generatesForce |
P173467
|
FINISHED |
| Object | Coulomb force |
—
|
NE NERFINISHED |
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: Coulomb force | Statement: [Coulomb potential, generatesForce, Coulomb force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generatesForce Context triple: [Coulomb potential, generatesForce, Coulomb force]
-
A.
usesForcesFrom
Indicates that one entity applies or derives physical forces from another entity as part of its operation or behavior.
-
B.
ledForcesFrom
Indicates that one entity commanded or directed military or armed forces originating from another entity or location.
-
C.
sendsForcesTo
Indicates that one entity dispatches or deploys military or security forces to another entity or location.
-
D.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
E.
governingForceOf
Indicates that one entity functions as the primary controlling or directing influence over another entity’s behavior, state, or dynamics.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 30, 2026, 11:59 p.m.