Triple
T29122695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-47 |
E738130
|
entity |
| Predicate | carriedPressurizedModule |
P133758
|
FINISHED |
| Object | Spacelab-J laboratory |
—
|
NE NERFINISHED |
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: Spacelab-J laboratory | Statement: [STS-47, carriedPressurizedModule, Spacelab-J laboratory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedPressurizedModule Context triple: [STS-47, carriedPressurizedModule, Spacelab-J laboratory]
-
A.
pressurizedCargoModuleSupplier
Indicates a supplier relationship in which one entity provides or manufactures pressurized cargo modules for another entity.
-
B.
usedPressurizedModule
Indicates that an entity has operated or occupied a pressurized module as part of its activities or mission.
-
C.
pressurizedModules
chosen
Indicates that the related modules are maintained at a controlled internal pressure suitable for human occupancy or specific operational conditions.
-
D.
pressurizedModuleType
Indicates the specific kind or classification of a pressurized module associated with an entity.
-
E.
isPressurizedCargoCarrier
Indicates that the entity functions as a cargo carrier whose internal space is maintained at a controlled pressure.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 11:26 a.m.