Triple
T21243308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redfield ratio |
E523536
|
entity |
| Predicate | hasCanonicalAtomicRatio |
P143344
|
FINISHED |
| Object | C:N:P = 106:16: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: C:N:P = 106:16:1 | Statement: [Redfield ratio, hasCanonicalAtomicRatio, C:N:P = 106:16:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalAtomicRatio Context triple: [Redfield ratio, hasCanonicalAtomicRatio, C:N:P = 106:16:1]
-
A.
hasAtomicNumber
Indicates that one entity is the chemical element whose atomic number (number of protons in its nucleus) is given by the other entity.
-
B.
hasChemicalFormula
Indicates that one entity (typically a chemical substance) is characterized by or associated with a specific chemical formula representing its elemental composition.
-
C.
hasAtomicRadius
Indicates that an entity possesses a specific atomic radius value, representing the size of its atoms.
-
D.
isMonoisotopic
Indicates that something consists of or relates to only a single isotope, without isotopic variation.
-
E.
hasCanonicalRepresentation
Indicates that one entity is the standard or authoritative form in which another entity is represented.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7352507448190ba1f14cef16d69be |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:47 p.m.