Triple

T31597219
Position Surface form Disambiguated ID Type / Status
Subject Embraer Praetor 500 E806249 entity
Predicate landingDistance_ft P10875 FINISHED
Object approximately 2621 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 2621 | Statement: [Embraer Praetor 500, landingDistance_ft, approximately 2621]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: landingDistance_ft
Context triple: [Embraer Praetor 500, landingDistance_ft, approximately 2621]
  • A. landingDistance chosen
    Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
  • B. landingDistanceSTOL
    Indicates the distance required for an aircraft to land and come to a stop when using short takeoff and landing (STOL) procedures.
  • C. takeoffDistanceM
    Indicates the distance, measured in meters, required for an aircraft (or similar vehicle) to accelerate and lift off from the ground.
  • D. distanceOfTouchdown
    Indicates the measured distance from the line of scrimmage to the point where a touchdown is scored.
  • E. takeoffDistanceCharacteristic
    Indicates the relationship between an aircraft (or flight operation) and a characteristic describing the distance required or used for takeoff.
  • 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_69f348d54ccc8190a03b5df9a2b40b25 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a835ecc48190912306b14b3e2909 completed May 3, 2026, 1:43 a.m.
PD Predicate disambiguation batch_69f6a75656e081908739ed9e2f600e42 completed May 3, 2026, 1:39 a.m.
Created at: April 30, 2026, 10:31 p.m.