Triple
T14274137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M142 launcher module |
E353870
|
entity |
| Predicate | reloadTime |
P113533
|
FINISHED |
| Object | rapid pod exchange |
—
|
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: rapid pod exchange | Statement: [M142 launcher module, reloadTime, rapid pod exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reloadTime Context triple: [M142 launcher module, reloadTime, rapid pod exchange]
-
A.
redeploymentTime
Indicates the amount of time required to redeploy or reassign a resource, system, or unit from one operational state or location to another.
-
B.
revivalEndTime
Indicates the point in time at which a revival process, event, or restored state comes to an end.
-
C.
bootTimeCharacteristic
Indicates the duration or properties of the time it takes a system or device to start up from an inactive state.
-
D.
resolutionTime
Indicates the duration taken to resolve an issue, task, or request from its initiation to its completion.
-
E.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6582f5308190969f4cfd724d9139 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.