Triple
T189507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | deuteron |
E3686
|
entity |
| Predicate | hasLifetime |
P585
|
FINISHED |
| Object | >10^28 years (effectively stable) |
—
|
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 (effectively stable) | Statement: [deuteron, hasLifetime, >10^28 years (effectively stable)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLifetime Context triple: [deuteron, hasLifetime, >10^28 years (effectively stable)]
-
A.
isShortLived
Indicates that an entity exists or remains in a particular state for only a brief or limited period of time.
-
B.
lifespan
chosen
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
C.
hasResidenceTime
Indicates the duration for which something remains or stays within a particular place, system, or state.
-
D.
livedDuring
Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
-
E.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2594c385481909e1e088e45c460a4 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25673ce3c8190b1a3df5b814a0595 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.