Triple
T34902706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salyut 2 |
E1006633
|
entity |
| Predicate | hadPressurizedVolume |
P51547
|
FINISHED |
| Object | about 90 cubic metres |
—
|
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: about 90 cubic metres | Statement: [Salyut 2, hadPressurizedVolume, about 90 cubic metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPressurizedVolume Context triple: [Salyut 2, hadPressurizedVolume, about 90 cubic metres]
-
A.
pressurizedVolume
chosen
Indicates that a specified volume is maintained at a pressure different from ambient (typically higher), often as part of a controlled or sealed system.
-
B.
pressurizedVariant
Indicates that one entity is a pressurized version or configuration of another entity.
-
C.
pressurized
Indicates that one entity exerts or maintains pressure on another, often creating a constrained or high-pressure condition.
-
D.
payloadPressurization
Indicates that a system or process is applying and maintaining a specified internal pressure within a payload or payload compartment.
-
E.
usedPressurizedModule
Indicates that an entity has operated or occupied a pressurized module as part of its activities or mission.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.