Triple
T36484735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Experiment Module |
E898905
|
entity |
| Predicate | firstElementLaunched |
P29648
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Japanese Experiment Module, firstElementLaunched, 2008]
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 (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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.