Triple
T11802738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 777-8 |
E280666
|
entity |
| Predicate | designRange_km |
P19870
|
FINISHED |
| Object | over 16000 |
—
|
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: over 16000 | Statement: [Boeing 777-8, designRange_km, over 16000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designRange_km Context triple: [Boeing 777-8, designRange_km, over 16000]
-
A.
range_km
chosen
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
-
B.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
C.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
D.
dimensions_km
Indicates the physical size or extent of something measured in kilometers, typically specifying one or more linear dimensions (e.g., length, width, height).
-
E.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.