Triple
T19745918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-112 |
E474249
|
entity |
| Predicate | issModuleInstalled |
P137167
|
FINISHED |
| Object | S1 truss |
—
|
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: S1 truss | Statement: [STS-112, issModuleInstalled, S1 truss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issModuleInstalled Context triple: [STS-112, issModuleInstalled, S1 truss]
-
A.
supportsModule
Indicates that one entity provides compatibility, functionality, or resources necessary for another entity’s module to operate or be used.
-
B.
issModuleVisited
Indicates that a specific ISS module has been entered or visited by an entity (such as an astronaut or spacecraft) at least once.
-
C.
ISSModuleName
Indicates that an entity is identified by the specific name of an International Space Station (ISS) module.
-
D.
hasServiceModule
Indicates that an entity is equipped with, or associated with, a specific service module that provides supporting or auxiliary functions.
-
E.
includesModuleProvider
Indicates that one entity contains or makes use of another entity that serves as a provider of a specific module or modular functionality.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529387ac819094e4d66d630e8b98 |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.