Triple
T37442821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCSS |
E930464
|
entity |
| Predicate | usesEngineCycle |
P188321
|
FINISHED |
| Object | expander cycle |
—
|
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: expander cycle | Statement: [DCSS, usesEngineCycle, expander cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEngineCycle Context triple: [DCSS, usesEngineCycle, expander cycle]
-
A.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
B.
firstStageEngineCycle
Indicates that one engine cycle is used as the primary or initial propulsion stage in a multi-stage launch or propulsion system.
-
C.
testedEngine
Indicates that an engine has undergone a testing process to evaluate its performance, functionality, or reliability.
-
D.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
E.
originatesFromEngine
Indicates that something has its source, cause, or production in a particular engine.
- F. None of above. chosen
Provenance (4 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.