Triple
T19096387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yak-130 |
E467416
|
entity |
| Predicate | externalPayloadCapacity |
P134353
|
FINISHED |
| Object | 3000 kg |
—
|
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: 3000 kg | Statement: [Yak-130, externalPayloadCapacity, 3000 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: externalPayloadCapacity Context triple: [Yak-130, externalPayloadCapacity, 3000 kg]
-
A.
gtoPayloadCapacity
Indicates the maximum payload mass an object (typically a launch vehicle) can deliver to a geostationary transfer orbit.
-
B.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
C.
leoPayloadCapacity
Indicates the maximum payload mass or capacity that can be delivered to Low Earth Orbit (LEO) in the context of a launch vehicle or space mission.
-
D.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
E.
slingLoadCapacity
Indicates the maximum weight or load that can be safely carried or supported using a sling.
- F. None of above. chosen
Provenance (4 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e369aeac81908913c21f4c234c8e |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.