Triple
T13074253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonov An-124 Ruslan |
E329530
|
entity |
| Predicate | pressurizedCargoHold |
P105528
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Antonov An-124 Ruslan, pressurizedCargoHold, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressurizedCargoHold Context triple: [Antonov An-124 Ruslan, pressurizedCargoHold, true]
-
A.
pressurizedCargoModuleSupplier
Indicates a supplier relationship in which one entity provides or manufactures pressurized cargo modules for another entity.
-
B.
isPressurizedCargoCarrier
chosen
Indicates that the entity functions as a cargo carrier whose internal space is maintained at a controlled pressure.
-
C.
pressurizedCabin
Indicates that an enclosed space, typically in a vehicle or structure, is maintained at a controlled air pressure different from the outside environment.
-
D.
unpressurizedCargoCapability
Indicates the ability of an entity to carry or transport cargo in an unpressurized space or compartment.
-
E.
cargoHoldVolume
Indicates the total internal volume available within a cargo hold for storing goods or materials.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d981160e388190bab942a2ded2903e |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.