Triple
T14133291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream G600 |
E350222
|
entity |
| Predicate | maximumRange_nm |
P14301
|
FINISHED |
| Object | 6500 |
—
|
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: 6500 | Statement: [Gulfstream G600, maximumRange_nm, 6500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRange_nm Context triple: [Gulfstream G600, maximumRange_nm, 6500]
-
A.
wavelengthRangeLowerBoundMicrometers
Indicates the minimum wavelength value, expressed in micrometers, that defines the lower limit of a wavelength range for the related entity or measurement.
-
B.
maximumReach
chosen
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
C.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
-
D.
energyRangeUpperBound_MeV
Indicates the maximum energy value, expressed in mega–electronvolts (MeV), that defines the upper limit of an energy range in the relationship.
-
E.
maximumWorkingDistance
Indicates the greatest allowable or effective distance at which the specified work, operation, or interaction can be performed.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610cece88190b4a86500677e5938 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 11:34 p.m.