Triple
T26990666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rydberg series |
E679852
|
entity |
| Predicate | fundamentalTo |
P3636
|
FINISHED |
| Object | understanding atomic energy levels |
—
|
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: understanding atomic energy levels | Statement: [Rydberg series, fundamentalTo, understanding atomic energy levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundamentalTo Context triple: [Rydberg series, fundamentalTo, understanding atomic energy levels]
-
A.
isFundamental
Indicates that something is a basic, essential, or foundational element upon which other things depend or are built.
-
B.
foundation
Indicates that one entity serves as the base, support, or underlying basis upon which another entity is built, established, or depends.
-
C.
underpins
chosen
Indicates that one entity serves as the fundamental basis, support, or justification for another.
-
D.
underlies
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
-
E.
becameBasisOf
Indicates that one entity served as the foundational source, model, or starting point upon which another entity was developed, derived, or established.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6218eac6c81909b76d7ea67b47e8f |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:51 a.m.