Triple
T20703857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAC One-Eleven (re-engined variants) |
E508847
|
entity |
| Predicate | operationalBenefit |
P487
|
FINISHED |
| Object | improved climb performance |
—
|
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 climb performance | Statement: [BAC One-Eleven (re-engined variants), operationalBenefit, improved climb performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalBenefit Context triple: [BAC One-Eleven (re-engined variants), operationalBenefit, improved climb performance]
-
A.
benefitsOperator
Indicates that one entity provides an advantage, profit, or positive outcome to an operator entity.
-
B.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
C.
benefits
chosen
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
D.
benefice
Indicates that one entity grants or bestows a benefit, favor, or advantage upon another.
-
E.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c18dbda081908217dcb61cbf7ba4 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:13 p.m.