Triple
T22319979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-32A |
E551755
|
entity |
| Predicate | maximumTakeoffWeightClass |
P54377
|
FINISHED |
| Object | around 115,000 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: around 115,000 kg | Statement: [C-32A, maximumTakeoffWeightClass, around 115,000 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTakeoffWeightClass Context triple: [C-32A, maximumTakeoffWeightClass, around 115,000 kg]
-
A.
takeoffWeightClass
chosen
Indicates the classification of an aircraft or vehicle based on its weight at the time of takeoff.
-
B.
maximumTakeoffWeight
Indicates the greatest allowable weight an aircraft can have at the start of its takeoff roll under specified conditions.
-
C.
aircraftSizeClass
Indicates the size category or class an aircraft belongs to based on its physical dimensions or capacity.
-
D.
designedTakeoffWeight_tonnes
Indicates the aircraft’s intended maximum takeoff weight, measured in metric tonnes, as specified in its design.
-
E.
maximumTonnageLimitedBy
Indicates that the maximum allowable tonnage of one entity is constrained or capped by the capacity or limit specified by another 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15763bf0881908d859f85b4a6ce28 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.