Triple
T6202122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fokker F28 |
E138657
|
entity |
| Predicate | maximumTakeoffWeightRange |
P10870
|
FINISHED |
| Object | 32–37 tonnes |
—
|
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: 32–37 tonnes | Statement: [Fokker F28, maximumTakeoffWeightRange, 32–37 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTakeoffWeightRange Context triple: [Fokker F28, maximumTakeoffWeightRange, 32–37 tonnes]
-
A.
maximumTakeoffWeight
chosen
Indicates the greatest allowable weight an aircraft can have at the start of its takeoff roll under specified conditions.
-
B.
takeoffWeightClass
Indicates the classification of an aircraft or vehicle based on its weight at the time of takeoff.
-
C.
maximumTonnageLimitedBy
Indicates that the maximum allowable tonnage of one entity is constrained or capped by the capacity or limit specified by another entity.
-
D.
takeoffDistanceAtMaxWeight
Indicates the distance required for an aircraft to take off when operating at its maximum allowable weight.
-
E.
takeoffWeightOnRecordFlight
Indicates the recorded takeoff weight associated with a specific flight.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626a32908190a3332008aee2e4a9 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.