Triple
T35561150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WISE |
E1027637
|
entity |
| Predicate | cryogenDepletionDate |
P108916
|
FINISHED |
| Object | 2010-10 |
—
|
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: 2010-10 | Statement: [WISE, cryogenDepletionDate, 2010-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cryogenDepletionDate Context triple: [WISE, cryogenDepletionDate, 2010-10]
-
A.
cryogenDepletion
Indicates that the amount of cryogenic coolant has been reduced or exhausted, typically impairing the normal operation of the associated system or instrument.
-
B.
endOfHeliumCryogen
chosen
Indicates the point in time or condition at which the available helium cryogen is fully depleted or no longer usable.
-
C.
cryogen
Indicates that an entity is preserved or maintained at extremely low temperatures, typically to halt biological or chemical processes.
-
D.
isCryogenic
Indicates that something operates at, is designed for, or involves extremely low (cryogenic) temperatures.
-
E.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.