Triple
T24917561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luftwaffe bombers |
E624029
|
entity |
| Predicate | roleInBlitzkrieg |
P108011
|
FINISHED |
| Object | support of fast-moving ground forces |
—
|
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: support of fast-moving ground forces | Statement: [Luftwaffe bombers, roleInBlitzkrieg, support of fast-moving ground forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBlitzkrieg Context triple: [Luftwaffe bombers, roleInBlitzkrieg, support of fast-moving ground forces]
-
A.
roleInOperationWeserübung
Indicates the specific role or function an entity held in the context of Operation Weserübung.
-
B.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
-
C.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
D.
roleInWarOrConflict
chosen
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
E.
roleInTimeWar
Indicates that an entity held a specific role or function during the period or events referred to as the Time War.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 5:28 a.m.