Triple
T20881395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commando |
E514158
|
entity |
| Predicate | hasMaximumTakeoffWeight |
P10870
|
FINISHED |
| Object | approximately 49,700 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: approximately 49,700 lb | Statement: [Commando, hasMaximumTakeoffWeight, approximately 49,700 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumTakeoffWeight Context triple: [Commando, hasMaximumTakeoffWeight, approximately 49,700 lb]
-
A.
maximumTakeoffWeight
chosen
Indicates the greatest allowable weight an aircraft can have at the start of its takeoff roll under specified conditions.
-
B.
designedTakeoffWeight_tonnes
Indicates the aircraft’s intended maximum takeoff weight, measured in metric tonnes, as specified in its design.
-
C.
takeoffDistanceAtMaxWeight
Indicates the distance required for an aircraft to take off when operating at its maximum allowable weight.
-
D.
takeoffWeightClass
Indicates the classification of an aircraft or vehicle based on its weight at the time of takeoff.
-
E.
hasTakeoffAndLandingCapability
Indicates that an entity possesses the ability to both take off and land, typically under its own operational power or design.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67a33548190b0f5ba58b001d387 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.