Triple
T33867819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joule’s law of heating |
E868104
|
entity |
| Predicate | hasAlternativePowerForm |
P194201
|
FINISHED |
| Object | P = V I |
—
|
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: P = V I | Statement: [Joule’s law of heating, hasAlternativePowerForm, P = V I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativePowerForm Context triple: [Joule’s law of heating, hasAlternativePowerForm, P = V I]
-
A.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
derivesPowerFrom
Indicates that one entity obtains or is granted its power, authority, or energy as a result of another entity.
-
D.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
-
E.
modeOfPower
Indicates the type or method of power or energy by which an entity operates or is driven.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: May 1, 2026, 1:47 a.m.