Triple
T296279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-17 Globemaster III |
E6098
|
entity |
| Predicate | rangeWithMaxPayload |
P5433
|
FINISHED |
| Object | about 4,500 km |
—
|
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: about 4,500 km | Statement: [C-17 Globemaster III, rangeWithMaxPayload, about 4,500 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeWithMaxPayload Context triple: [C-17 Globemaster III, rangeWithMaxPayload, about 4,500 km]
-
A.
rangeCapability
chosen
Indicates the maximum distance or extent over which an entity can effectively operate, function, or exert its effect.
-
B.
rangeType
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
C.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
-
D.
setsMaximum
Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
-
E.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea4778cc8190be7b648a82542891 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e937af888190a0960708f09ae033 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.