Triple
T31898260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coulomb potential |
E814348
|
entity |
| Predicate | isTimeIndependent |
P157747
|
FINISHED |
| Object | for static charges |
—
|
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: for static charges | Statement: [Coulomb potential, isTimeIndependent, for static charges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTimeIndependent Context triple: [Coulomb potential, isTimeIndependent, for static charges]
-
A.
isHomogeneousInTime
chosen
Indicates that the relationship or property remains uniform and unchanged over time.
-
B.
isMetricIndependent
Indicates that the relationship or property holds regardless of the specific metric or distance function chosen on the underlying space.
-
C.
timeDependence
Indicates that one entity’s state, value, or behavior is determined by or varies as a function of another entity over time.
-
D.
isIndependent
Indicates that an entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
E.
hasIndependentVariable
Indicates that one entity functions as the independent variable that influences or determines another entity in a relationship or experiment.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b166b4788190997dc7d7b865a428 |
completed | May 3, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:59 p.m.