Triple
T14835620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream G500 |
E348821
|
entity |
| Predicate | maximumRangeKilometres |
P19870
|
FINISHED |
| Object | 9630 |
—
|
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: 9630 | Statement: [Gulfstream G500, maximumRangeKilometres, 9630]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumRangeKilometres Context triple: [Gulfstream G500, maximumRangeKilometres, 9630]
-
A.
range_km
chosen
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
-
B.
maximumRangeNauticalMiles
Indicates the greatest distance, measured in nautical miles, that something can travel or operate under specified conditions.
-
C.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
D.
maximumReach
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
E.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded076ac9c8190a05cabec5e87d207 |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:52 a.m.