Triple
T35382237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lippisch DM-1 |
E1022680
|
entity |
| Predicate | constructionStatusAtWarEnd |
P194147
|
FINISHED |
| Object | nearly complete |
—
|
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: nearly complete | Statement: [Lippisch DM-1, constructionStatusAtWarEnd, nearly complete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionStatusAtWarEnd Context triple: [Lippisch DM-1, constructionStatusAtWarEnd, nearly complete]
-
A.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
B.
interiorStatusAfterWar
Indicates the condition or state of a place’s interior following the events of a war.
-
C.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
-
D.
warEndedHere
Indicates that a particular war or armed conflict came to its conclusion at this location.
-
E.
lastWarEnd
Indicates that a specified war or conflict has reached its conclusion at a particular time or event.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69fd64bb345c819096a35c72784a8ce3 |
completed | May 8, 2026, 4:21 a.m. |
Created at: May 3, 2026, 4:03 p.m.