Triple
T4486034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | farad |
E107240
|
entity |
| Predicate | SIBaseExpression |
P51567
|
FINISHED |
| Object | s^4·A^2·m^-2·kg^-1 |
—
|
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: s^4·A^2·m^-2·kg^-1 | Statement: [farad, SIBaseExpression, s^4·A^2·m^-2·kg^-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SIBaseExpression Context triple: [farad, SIBaseExpression, s^4·A^2·m^-2·kg^-1]
-
A.
isPartOfExpression
Indicates that something functions as a component or constituent element within a larger expression.
-
B.
hasExpression
Indicates that an entity displays or possesses a particular facial or emotional expression.
-
C.
entersExpression
Indicates that one entity moves into, penetrates, or passes through another entity or defined space.
-
D.
coordinateExpression
Indicates that one expression is syntactically or semantically coordinated with another, typically as part of a compound structure (e.g., joined by "and" or "or").
-
E.
usedInExpression
chosen
Indicates that one entity (typically a term, symbol, or construct) is employed as a component within another entity that represents an expression.
- 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.