Triple
T16492808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electron |
E400606
|
entity |
| Predicate | hasUpperLimitOnLifetime |
P99
|
FINISHED |
| Object | >10^28 years |
—
|
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: >10^28 years | Statement: [Electron, hasUpperLimitOnLifetime, >10^28 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperLimitOnLifetime Context triple: [Electron, hasUpperLimitOnLifetime, >10^28 years]
-
A.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
B.
hasLifetimeStatus
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
-
C.
hasLimitSet
Indicates that there is a defined boundary, range, or constraint applied to something.
-
D.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
E.
hasLimitation
chosen
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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e30cb648190a52cb32896c4ac5a |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:13 a.m.