Triple
T10043337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 176 |
E205348
|
entity |
| Predicate | originatedInConflict |
P89805
|
FINISHED |
| Object | pre–World War II German rearmament |
—
|
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: pre–World War II German rearmament | Statement: [Heinkel He 176, originatedInConflict, pre–World War II German rearmament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedInConflict Context triple: [Heinkel He 176, originatedInConflict, pre–World War II German rearmament]
-
A.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
-
B.
basedInDuringConflict
Indicates that an entity is located or headquartered in a particular place for the duration of a specified conflict or war.
-
C.
builtDuringConflict
chosen
Indicates that the construction of one entity occurred while a specified conflict or war was taking place.
-
D.
originatingConflict
Indicates the conflict or dispute from which another event, situation, or relationship initially arises or is caused.
-
E.
militaryConflictIn
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf60a2208190846e57b5f5649307 |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:55 p.m.