Triple
T216502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pauling electronegativity scale |
E4115
|
entity |
| Predicate | definedFrom |
P909
|
FINISHED |
| Object | heteronuclear bond energies |
—
|
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: heteronuclear bond energies | Statement: [Pauling electronegativity scale, definedFrom, heteronuclear bond energies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedFrom Context triple: [Pauling electronegativity scale, definedFrom, heteronuclear bond energies]
-
A.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
definedOn
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
C.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
D.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
E.
differentiatedFrom
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
- 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.