Triple

T25867023
Position Surface form Disambiguated ID Type / Status
Subject Gulfstream G550 E651644 entity
Predicate maximumLandingWeight P165014 FINISHED
Object 34019 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: 34019 kg | Statement: [Gulfstream G550, maximumLandingWeight, 34019 kg]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maximumLandingWeight
Context triple: [Gulfstream G550, maximumLandingWeight, 34019 kg]
  • A. maximumTakeoffWeight
    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. 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. weightLimitInKilograms
    Indicates the maximum allowable weight for something, expressed in kilograms.
  • 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_69e7ab3a199c81909227cb964cacfe24 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f65705a3048190a3728b695ba2ae65 completed May 2, 2026, 7:56 p.m.
PD Predicate disambiguation batch_69f651a731508190bb0c8c2462eba224 completed May 2, 2026, 7:33 p.m.
PDg Predicate description generation batch_69f6562ef4e4819082ce6abd41b74dc5 completed May 2, 2026, 7:53 p.m.
Created at: April 22, 2026, 8:07 a.m.