Triple
T13634416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-334 |
E325809
|
entity |
| Predicate | designedTakeoffWeight_tonnes |
P111390
|
FINISHED |
| Object | 47 |
—
|
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: 47 | Statement: [Tupolev Tu-334, designedTakeoffWeight_tonnes, 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedTakeoffWeight_tonnes Context triple: [Tupolev Tu-334, designedTakeoffWeight_tonnes, 47]
-
A.
maximumTakeoffWeight
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.
takeoffDistanceAtMaxWeight
Indicates the distance required for an aircraft to take off when operating at its maximum allowable weight.
-
D.
takeoffDistanceM
Indicates the distance, measured in meters, required for an aircraft (or similar vehicle) to accelerate and lift off from the ground.
-
E.
takeoffCharacteristic
Indicates the specific properties or conditions associated with how an entity takes off, such as its manner, performance, or requirements during takeoff.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc6043e148190a2a25f929cfa35e5 |
completed | April 12, 2026, 4:19 p.m. |
Created at: April 9, 2026, 9:51 p.m.