Triple
T216486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pauling electronegativity scale |
E4115
|
entity |
| Predicate | sodiumValueApprox |
P9717
|
FINISHED |
| Object | 0.93 |
—
|
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: 0.93 | Statement: [Pauling electronegativity scale, sodiumValueApprox, 0.93]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sodiumValueApprox Context triple: [Pauling electronegativity scale, sodiumValueApprox, 0.93]
-
A.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
B.
hasSalinityRange
Indicates the range of salinity values within which something (such as a substance, environment, or organism) is present, applicable, or able to function.
-
C.
salinity
Indicates the concentration of dissolved salts present in or affecting something, typically a body of water or environment.
-
D.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
E.
hasHigherSalinityThan
Indicates that one entity has a greater concentration of dissolved salts than 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25dcba5148190ab80fd14c7cf4bb4 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.