Triple
T216505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pauling electronegativity scale |
E4115
|
entity |
| Predicate | symbolForElectronegativity |
P129
|
FINISHED |
| Object | χ |
—
|
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: χ | Statement: [Pauling electronegativity scale, symbolForElectronegativity, χ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForElectronegativity Context triple: [Pauling electronegativity scale, symbolForElectronegativity, χ]
-
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.
hasProtonNumber
Indicates that an entity (typically a chemical element or atom) possesses a specific number of protons in its nucleus.
-
C.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
D.
hasNeutronNumber
Indicates that an entity (typically an atom or nuclide) has a specified number of neutrons in its nucleus.
-
E.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
- 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_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. |
Created at: Feb. 28, 2026, 2:53 a.m.