Triple
T33131097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Learjet 85 |
E847870
|
entity |
| Predicate | intendedRange_km |
P19870
|
FINISHED |
| Object | 4800 |
—
|
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: 4800 | Statement: [Learjet 85, intendedRange_km, 4800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRange_km Context triple: [Learjet 85, intendedRange_km, 4800]
-
A.
range_km
chosen
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
-
B.
typicalRangeMinimum_km
Indicates the minimum distance, in kilometers, that is typically observed or expected within a given range for the relationship or measurement in question.
-
C.
latitudeRangeApproximate
Indicates that the latitude of an entity falls within an approximate or loosely bounded range, rather than an exact or strictly defined interval.
-
D.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
E.
downrangeDistance_km
Indicates the horizontal distance, measured in kilometers, that an object has traveled along its ground track from a defined launch or reference point.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 1:27 a.m.