Triple
T35382234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lippisch DM-1 |
E1022680
|
entity |
| Predicate | intendedSuccessorType |
P98729
|
FINISHED |
| Object | rocket-powered interceptor |
—
|
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: rocket-powered interceptor | Statement: [Lippisch DM-1, intendedSuccessorType, rocket-powered interceptor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedSuccessorType Context triple: [Lippisch DM-1, intendedSuccessorType, rocket-powered interceptor]
-
A.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
B.
intendedSuccessorTo
chosen
Indicates that one entity is meant or designated to follow, replace, or take over the role or position of another entity in the future.
-
C.
successorOnType
Indicates that one entity directly follows another in an ordered sequence defined by a specific type or category.
-
D.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
E.
successorSpecification
Indicates that one specification is defined as the direct successor or follow-up version of another specification.
- 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_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:03 p.m.