Triple
T18561568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salyut 7 |
E453652
|
entity |
| Predicate | pressurisedVolume |
P51547
|
FINISHED |
| Object | 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: 90 cubic metres | Statement: [Salyut 7, pressurisedVolume, 90 cubic metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressurisedVolume Context triple: [Salyut 7, pressurisedVolume, 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.
volumeOf
Indicates the quantitative three-dimensional space occupied by an entity or contained within an object.
-
C.
pressurized
Indicates that one entity exerts or maintains pressure on another, often creating a constrained or high-pressure condition.
-
D.
chamberPressure_MPa
Indicates the pressure within a chamber, measured in megapascals (MPa), during a specified process or state.
-
E.
pressureCapability
Indicates the maximum pressure an entity can safely exert, withstand, or operate under within a given context.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5380a46f08190afe7ca2ddfe209d5 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:42 a.m.