Triple
T8405061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CH-53E Super Stallion |
E198473
|
entity |
| Predicate | externalLiftCapacity |
P68727
|
FINISHED |
| Object | over 30,000 lb |
—
|
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: over 30,000 lb | Statement: [CH-53E Super Stallion, externalLiftCapacity, over 30,000 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: externalLiftCapacity Context triple: [CH-53E Super Stallion, externalLiftCapacity, over 30,000 lb]
-
A.
hasCraneCapacity
chosen
Indicates that an entity possesses a crane with a specified lifting capacity or load-handling capability.
-
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.
hasLift
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
E.
hasLiftType
Indicates the specific type or category of lift associated with an entity.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83116bf48190894bd5d5465520ef |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.