Triple
T22837288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spacelab Life Sciences-2 |
E565980
|
entity |
| Predicate | includedPayload |
P16605
|
FINISHED |
| Object | pressurized Spacelab module |
—
|
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: pressurized Spacelab module | Statement: [Spacelab Life Sciences-2, includedPayload, pressurized Spacelab module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedPayload Context triple: [Spacelab Life Sciences-2, includedPayload, pressurized Spacelab module]
-
A.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
B.
includesPayment
Indicates that one entity contains, involves, or provides a monetary payment as part of its terms, contents, or execution.
-
C.
secondaryPayload
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
-
D.
requiredPayload
Indicates that a specific payload must be provided or present for an action, process, or relationship to be valid or successfully executed.
-
E.
includedWith
chosen
Indicates that one entity is provided or packaged together as part of another entity.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e303cec81909c5c118dc8c93354 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.