Triple
T16921052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schiaparelli EDM lander |
E410443
|
entity |
| Predicate | designedLifetimeAfterLanding |
P8105
|
FINISHED |
| Object | a few days |
—
|
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: a few days | Statement: [Schiaparelli EDM lander, designedLifetimeAfterLanding, a few days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedLifetimeAfterLanding Context triple: [Schiaparelli EDM lander, designedLifetimeAfterLanding, a few days]
-
A.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
B.
exceededDesignLifetime
Indicates that an entity has operated beyond the duration or usage limits specified in its original design.
-
C.
designLifetime
chosen
Indicates the intended duration or operational period for which something is designed to function as specified.
-
D.
designedForLifecycle
Indicates that something has been intentionally created or configured to support, align with, or optimize a particular lifecycle or set of lifecycle stages.
-
E.
diesAfter
Indicates that one entity dies at a later time than another entity.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdee252c81908621b2ca897416e9 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.