Triple
T15432411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohm's law for electrical conduction |
E369671
|
entity |
| Predicate | symbolForVoltage |
P118760
|
FINISHED |
| Object | V |
—
|
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: V | Statement: [Ohm's law for electrical conduction, symbolForVoltage, V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForVoltage Context triple: [Ohm's law for electrical conduction, symbolForVoltage, V]
-
A.
signalVoltage
Indicates the electrical potential level carried by a signal in a circuit or communication channel.
-
B.
symbolForEnergy
Indicates that one entity serves as a symbolic representation or notation for the concept of energy associated with another entity.
-
C.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
-
D.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
E.
approximateVoltage
Indicates that one entity represents or provides a value that is close to, but not necessarily exactly equal to, the voltage of another entity.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03eda01cc8190843e23b260b8503c |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.