Triple
T25236300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paschen series |
E632344
|
entity |
| Predicate | PaαTransition |
P36477
|
FINISHED |
| Object | n=4 to n=3 |
—
|
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: n=4 to n=3 | Statement: [Paschen series, PaαTransition, n=4 to n=3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PaαTransition Context triple: [Paschen series, PaαTransition, n=4 to n=3]
-
A.
movementTransition
Indicates a change in an entity’s state of motion, such as starting, stopping, or altering the direction or mode of movement.
-
B.
powerTransitionTo
Indicates a change in control or authority from one entity to another as part of a succession or transfer of power.
-
C.
transitionTo
chosen
Indicates a change in state, condition, or phase from one defined status to another.
-
D.
formsTransitionBetween
Indicates that one state, phase, or condition serves as an intermediate link or bridge leading from one distinct state, phase, or condition to another.
-
E.
transitionProgram
Indicates a relationship where one entity serves as a program or structured process that facilitates another entity’s transition from one state, phase, or condition to another.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47df954cc8190ab223daad550fd0d |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:07 p.m.