Triple
T26990758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rydberg molecule |
E679853
|
entity |
| Predicate | lifetimeLimitedBy |
P69194
|
FINISHED |
| Object | collisional decay |
—
|
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: collisional decay | Statement: [Rydberg molecule, lifetimeLimitedBy, collisional decay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifetimeLimitedBy Context triple: [Rydberg molecule, lifetimeLimitedBy, collisional decay]
-
A.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
B.
limitedMembershipTo
Indicates that access, participation, or inclusion in something is restricted to a specific subset of entities or members.
-
C.
existencePeriod
chosen
Indicates the time span during which an entity exists or is valid.
-
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.
lifetimeUse
Indicates that the relationship or action concerns the total or cumulative extent of use of something over the entire duration of an entity’s existence or observation period.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6218fc6308190b1e3317de86703db |
completed | May 2, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:51 a.m.