Triple
T38092773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBM |
E951155
|
entity |
| Predicate | pressureRating |
P56372
|
FINISHED |
| Object | supports ISS internal pressure |
—
|
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: supports ISS internal pressure | Statement: [CBM, pressureRating, supports ISS internal pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressureRating Context triple: [CBM, pressureRating, supports ISS internal pressure]
-
A.
pressureCapability
chosen
Indicates the maximum pressure an entity can safely exert, withstand, or operate under within a given context.
-
B.
pressureRange
Indicates the range of pressure values within which a condition, process, or relationship is defined or valid.
-
C.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
D.
pressureTransmission
Indicates that pressure applied at one point in a system is conveyed or propagated to another point within that system.
-
E.
pressureBoundary
Indicates a boundary condition where pressure is specified or constrained at the interface between two regions or systems.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.