Triple
T4485837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faraday constant |
E107235
|
entity |
| Predicate | isEqualTo |
P6530
|
FINISHED |
| Object | Avogadro constant × elementary charge |
—
|
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: Avogadro constant × elementary charge | Statement: [Faraday constant, isEqualTo, Avogadro constant × elementary charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEqualTo Context triple: [Faraday constant, isEqualTo, Avogadro constant × elementary charge]
-
A.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
B.
equivalentTo
chosen
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
C.
modeEquals
Indicates that two compared entities share exactly the same mode or operational state.
-
D.
equalityCondition
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
-
E.
hasEquivalent
Indicates that two entities are considered equal in value, meaning, or function within 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.