Triple
T31597218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embraer Praetor 500 |
E806249
|
entity |
| Predicate | takeoffDistance_ft |
P172004
|
FINISHED |
| Object | approximately 4263 |
—
|
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 4263 | Statement: [Embraer Praetor 500, takeoffDistance_ft, approximately 4263]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takeoffDistance_ft Context triple: [Embraer Praetor 500, takeoffDistance_ft, approximately 4263]
-
A.
takeoffDistanceM
Indicates the distance, measured in meters, required for an aircraft (or similar vehicle) to accelerate and lift off from the ground.
-
B.
takeoffDistanceAtMaxWeight
Indicates the distance required for an aircraft to take off when operating at its maximum allowable weight.
-
C.
takeoffDistanceCharacteristic
Indicates the relationship between an aircraft (or flight operation) and a characteristic describing the distance required or used for takeoff.
-
D.
runwayLength
Indicates the length of a runway associated with an airport or airfield.
-
E.
landingDistanceSTOL
Indicates the distance required for an aircraft to land and come to a stop when using short takeoff and landing (STOL) procedures.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:31 p.m.