Triple
T21380407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grob G 109 |
E527335
|
entity |
| Predicate | glidePerformance |
P87917
|
FINISHED |
| Object | high glide ratio |
—
|
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: high glide ratio | Statement: [Grob G 109, glidePerformance, high glide ratio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glidePerformance Context triple: [Grob G 109, glidePerformance, high glide ratio]
-
A.
glideRatio
chosen
Indicates the ratio between horizontal distance traveled and vertical distance lost during a glide.
-
B.
climbPerformance
Indicates how effectively or rapidly an entity ascends or gains altitude relative to conditions or expectations.
-
C.
hasOffAxisPerformance
Indicates that an entity exhibits specific behavior or performance characteristics when observed or operated from an angle that is not aligned with its primary or intended axis.
-
D.
GPUPerformanceClaim
Indicates a statement asserting or characterizing the performance capabilities of a GPU, often in terms of speed, efficiency, or comparative advantage.
-
E.
performsWellOn
Indicates that one entity achieves good results or high performance when evaluated using, or operating within, another entity (such as a task, test, or environment).
- 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0cdab8c8190a7eebe6e5961ee75 |
completed | April 22, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:11 p.m.