Triple
T475310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airbus A320 family |
E9047
|
entity |
| Predicate | designRole |
P268
|
FINISHED |
| Object | short- to medium-range operations |
—
|
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: short- to medium-range operations | Statement: [Airbus A320 family, designRole, short- to medium-range operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designRole Context triple: [Airbus A320 family, designRole, short- to medium-range operations]
-
A.
designerOccupation
Indicates that one entity serves as the professional designer or design specialist for another entity.
-
B.
architecturalRole
Indicates the functional or design-related role that one entity plays within the structure, layout, or organization of another entity.
-
C.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
E.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03b5e5081908ee3dba9d19a6871 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edeed31881908cf43beed410572d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.