Triple
T757306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erla Maschinenwerk |
E15584
|
entity |
| Predicate | roleDuringWar |
P9463
|
FINISHED |
| Object | military aircraft manufacturer |
—
|
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: military aircraft manufacturer | Statement: [Erla Maschinenwerk, roleDuringWar, military aircraft manufacturer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDuringWar Context triple: [Erla Maschinenwerk, roleDuringWar, military aircraft manufacturer]
-
A.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
-
B.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
C.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
D.
peacetimeRole
Indicates the role, function, or duties an entity holds during periods of peace rather than during wartime or conflict.
-
E.
roleAtStalingrad
Indicates the specific role, position, or function an entity held in relation to the Battle of Stalingrad.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66ab4608190afcd81e6606c5116 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.