Triple
T26281621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream G800 |
E660712
|
entity |
| Predicate | fuelEfficiencyComparedToPredecessors |
P41013
|
FINISHED |
| Object | improved |
—
|
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: improved | Statement: [Gulfstream G800, fuelEfficiencyComparedToPredecessors, improved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelEfficiencyComparedToPredecessors Context triple: [Gulfstream G800, fuelEfficiencyComparedToPredecessors, improved]
-
A.
typicalEfficiencyComparedToPredecessor
chosen
Indicates how the usual or average efficiency of something compares to that of its predecessor.
-
B.
emissionsComparedToPredecessor
Indicates how the emissions of an entity compare in magnitude (e.g., higher, lower, or equal) to those of its immediate predecessor.
-
C.
technologyLevelComparedToPredecessor
Indicates how the technology level of an entity compares to that of its immediate predecessor.
-
D.
fuelEfficiency
Indicates how effectively an entity uses fuel to perform a given amount of work or travel a certain distance.
-
E.
comparedToPredecessor
Indicates that something is being evaluated or measured in relation to the thing that came immediately before 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e74cdf08190b753c3c10691a440 |
completed | May 2, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:01 p.m.