Triple
T38479385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block I Command and Service Module |
E915628
|
entity |
| Predicate | lifeSupportDuration |
P190008
|
FINISHED |
| Object | upTo14DaysNominalDesign |
—
|
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: upTo14DaysNominalDesign | Statement: [Block I Command and Service Module, lifeSupportDuration, upTo14DaysNominalDesign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeSupportDuration Context triple: [Block I Command and Service Module, lifeSupportDuration, upTo14DaysNominalDesign]
-
A.
supportsLifespan
Indicates that one entity contributes to maintaining, extending, or enabling the full duration of another entity’s life or functional existence.
-
B.
lifeSupportRole
chosen
Indicates a role an entity plays in providing, managing, or supporting life-sustaining functions or systems for another entity.
-
C.
salvoDuration
Indicates the length of time that a salvo (a concentrated burst or sequence of actions, such as weapon fire) lasts.
-
D.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
E.
survivesFor
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.