Triple
T4486073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | farad |
E107240
|
entity |
| Predicate | hasInverseUnit |
P38095
|
FINISHED |
| Object | volt per coulomb |
—
|
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: volt per coulomb | Statement: [farad, hasInverseUnit, volt per coulomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInverseUnit Context triple: [farad, hasInverseUnit, volt per coulomb]
-
A.
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.
-
B.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
C.
isInternalUnitOf
Indicates that one unit functions as a subordinate or component part within the organizational structure of another unit.
-
D.
hasReverse
chosen
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
-
E.
isIntegerUnitIn
Indicates that one integer-valued unit is contained within, or belongs to, a specified larger unit or unit set.
- 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.