Triple
T36484735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Experiment Module |
E898905
|
entity |
| Predicate | firstElementLaunched |
—
|
GENERATED |
| Object | 2008 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstElementLaunched Context triple: [Japanese Experiment Module, firstElementLaunched, 2008]
-
A.
firstModuleLaunch
chosen
Indicates the event or relationship where the initial module of a system, project, or mission is launched or activated for the first time.
-
B.
firstTestLaunch
Indicates that an entity’s initial test launch event occurs, marking the first time it is experimentally deployed or sent into operation.
-
C.
firstLaunchMission
Indicates that a mission is the first launch associated with a particular object, program, or entity.
-
D.
firstActivatedIn
Indicates the point in time or context when an entity was initially activated or became operational.
-
E.
launchedFirstUnit
Indicates that one entity initiated and deployed the first unit of something (e.g., product, system, or mission) before any others.
- F. None of above.
Provenance (1 batch)
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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.