Triple
T1780801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airbus A340 |
E39285
|
entity |
| Predicate | designConfiguration |
P2093
|
FINISHED |
| Object | low-wing cantilever monoplane |
—
|
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: low-wing cantilever monoplane | Statement: [Airbus A340, designConfiguration, low-wing cantilever monoplane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designConfiguration Context triple: [Airbus A340, designConfiguration, low-wing cantilever monoplane]
-
A.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
B.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
C.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
D.
designSpecifiedBy
Indicates that the design or specification of one entity is defined, authored, or determined by another entity.
-
E.
configuration
chosen
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.