Triple
T35556591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lippisch Delta I |
E1027513
|
entity |
| Predicate | hasWingPlanform |
P183240
|
FINISHED |
| Object | triangular planform |
—
|
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: triangular planform | Statement: [Lippisch Delta I, hasWingPlanform, triangular planform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWingPlanform Context triple: [Lippisch Delta I, hasWingPlanform, triangular planform]
-
A.
hasWingOf
Indicates that one entity possesses or is associated with the wing that belongs to another entity.
-
B.
hasWingIn
Indicates that an entity possesses a wing that is located in or contained within another specified entity or structure.
-
C.
hasWingConfiguration
Indicates how an entity’s wings are arranged, structured, or configured relative to its body or to each other.
-
D.
hasWingFunction
Indicates that an entity possesses a wing and specifies the functional role or purpose that the wing serves.
-
E.
architectOfWing
Indicates that one entity served as the architect responsible for designing a particular wing of a building or structure.
- F. None of above. chosen
Provenance (4 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_69f76e014fd481909e9f04ac603a2aa9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.