Triple
T16807281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balmer series of hydrogen |
E408510
|
entity |
| Predicate | hasSeriesLimit |
P9149
|
FINISHED |
| Object | n → ∞ to n = 2 |
—
|
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 → ∞ to n = 2 | Statement: [Balmer series of hydrogen, hasSeriesLimit, n → ∞ to n = 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeriesLimit Context triple: [Balmer series of hydrogen, hasSeriesLimit, n → ∞ to n = 2]
-
A.
isLimitOf
chosen
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
B.
hasLimitedEditionSeries
Indicates that an entity is associated with a special, restricted-quantity series or collection.
-
C.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
D.
hasLimitSet
Indicates that there is a defined boundary, range, or constraint applied to something.
-
E.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cd1e8c8190a7a05ba255f711c7 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.