Triple
T4486049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | farad |
E107240
|
entity |
| Predicate | inverseQuantity |
P9781
|
FINISHED |
| Object | reactance at 1/(2πfC) |
—
|
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: reactance at 1/(2πfC) | Statement: [farad, inverseQuantity, reactance at 1/(2πfC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inverseQuantity Context triple: [farad, inverseQuantity, reactance at 1/(2πfC)]
-
A.
inverselyProportionalTo
chosen
Indicates that as the value of one quantity increases, the value of the other quantity decreases in such a way that their product remains constant.
-
B.
usesQuantity
Indicates that one entity employs or applies a specified amount or measure of another entity in performing an action or fulfilling a function.
-
C.
quantifies
Indicates that one entity expresses or specifies the amount, number, or degree of another entity.
-
D.
isInverseOf
Indicates that one relation reverses the direction of another, so that if the original relates A to B, its inverse relates B to A.
-
E.
quantificationType
Indicates the specific kind or category of quantity or measurement being applied in a given context.
- 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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd556d29f08190bab1e872dd7e819f |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:59 p.m.