Triple
T7198341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream G650 |
E168672
|
entity |
| Predicate | maximumRangeNauticalMiles |
P75759
|
FINISHED |
| Object | 7000 |
—
|
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: 7000 | Statement: [Gulfstream G650, maximumRangeNauticalMiles, 7000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRangeNauticalMiles Context triple: [Gulfstream G650, maximumRangeNauticalMiles, 7000]
-
A.
range_km
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
-
B.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
-
C.
maximumReach
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
D.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
E.
flightRangeFocus
Indicates that the relationship centers on the range or distance a flight can cover, emphasizing limitations or focus on how far the flight can travel.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92a5d288190955f703470e75bf3 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e8fd9b848190b2b1beea5698422b |
completed | March 27, 2026, 8:30 p.m. |
Created at: March 27, 2026, 2:52 p.m.