Triple
T35382231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lippisch DM-1 |
E1022680
|
entity |
| Predicate | developedFromConceptsOf |
P48732
|
FINISHED |
| Object | Lippisch P.13a |
—
|
NE NERFINISHED |
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: Lippisch P.13a | Statement: [Lippisch DM-1, developedFromConceptsOf, Lippisch P.13a]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedFromConceptsOf Context triple: [Lippisch DM-1, developedFromConceptsOf, Lippisch P.13a]
-
A.
developedFrom
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
B.
hasConceptualOrigin
chosen
Indicates that something conceptually originates from, is derived from, or is fundamentally based on another thing.
-
C.
historicallyDevelopedWith
Indicates that one entity evolved, emerged, or was formed over time in conjunction with or as a result of the development of another entity.
-
D.
developedAsReactionTo
Indicates that one entity was created, formed, or evolved specifically in response to the existence, influence, or impact of another entity.
-
E.
developedFromPeriod
Indicates that something originated, evolved, or was derived from a specified historical or temporal period.
- 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_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:03 p.m.