Triple
T25236291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paschen series |
E632344
|
entity |
| Predicate | energyLevelModel |
P160906
|
FINISHED |
| Object | Bohr model of hydrogen |
—
|
NE NERFINISHED |
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: Bohr model of hydrogen | Statement: [Paschen series, energyLevelModel, Bohr model of hydrogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyLevelModel Context triple: [Paschen series, energyLevelModel, Bohr model of hydrogen]
-
A.
energyLevel
Indicates the amount or intensity of energy possessed, produced, or exhibited by an entity in a given state or context.
-
B.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
C.
powerLevel
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
D.
energyPotential
Indicates a relationship where one entity possesses or confers the capacity to perform work or cause change (potential energy) relative to another entity or state.
-
E.
energyExchangeAbility
Indicates the capacity of one entity to transfer, share, or convert energy with another entity within a given context.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f60cd7b3e88190a1206958c0f0b225 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c32ce088190a620eb59d2499fa9 |
completed | May 2, 2026, 2:37 p.m. |
Created at: April 21, 2026, 1:07 p.m.