Triple
T31898259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coulomb potential |
E814348
|
entity |
| Predicate | hasEnergyDimension |
P56514
|
FINISHED |
| Object | joules |
—
|
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: joules | Statement: [Coulomb potential, hasEnergyDimension, joules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyDimension Context triple: [Coulomb potential, hasEnergyDimension, joules]
-
A.
dimensionOfEnergy
chosen
Indicates a relationship where a specified dimension or unit is associated with a particular measure or quantity of energy.
-
B.
hasOrderOfMagnitudeInJoules
Indicates that the quantity associated with an entity is approximately of a specified order of magnitude when measured in joules.
-
C.
hasEnergyConcept
Indicates that one entity is associated with, characterized by, or defined in terms of a particular concept of energy.
-
D.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
E.
hasEnergyResource
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
- 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_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 30, 2026, 11:59 p.m.