Triple
T35382186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lippisch P.13a |
E1022679
|
entity |
| Predicate | wingPlanform |
P6541
|
FINISHED |
| Object | sharp delta |
—
|
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: sharp delta | Statement: [Lippisch P.13a, wingPlanform, sharp delta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wingPlanform Context triple: [Lippisch P.13a, wingPlanform, sharp delta]
-
A.
wingArea
Indicates the total surface area covered by an entity’s wing or wings.
-
B.
wingConfiguration
chosen
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
C.
wingDesignBasisFor
Indicates that a particular wing design serves as the foundational reference or primary basis for another design, configuration, or analysis.
-
D.
architectOfWing
Indicates that one entity served as the architect responsible for designing a particular wing of a building or structure.
-
E.
wingSpanVariant
Indicates a relationship where one wing span measurement is a variant or alternative form of another wing span measurement.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.