Triple
T7918854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Functional Cargo Block |
E183892
|
entity |
| Predicate | isPressurized |
P51547
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Functional Cargo Block, isPressurized, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPressurized Context triple: [Functional Cargo Block, isPressurized, yes]
-
A.
pressurizedCabin
Indicates that an enclosed space, typically in a vehicle or structure, is maintained at a controlled air pressure different from the outside environment.
-
B.
pressurization
Indicates the process of applying or maintaining pressure on or within an object, system, or environment.
-
C.
usedPressurizedModule
Indicates that an entity has operated or occupied a pressurized module as part of its activities or mission.
-
D.
pressurizedCargoModuleSupplier
Indicates a supplier relationship in which one entity provides or manufactures pressurized cargo modules for another entity.
-
E.
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.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a8fbbb48190b50def4941761a31 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:05 p.m.