Triple
T37667470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 23 November 1939 |
E937858
|
entity |
| Predicate | GneisenauOperator |
P188527
|
FINISHED |
| Object | Kriegsmarine |
—
|
NE NERFINISHED |
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: Kriegsmarine | Statement: [Action of 23 November 1939, GneisenauOperator, Kriegsmarine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GneisenauOperator Context triple: [Action of 23 November 1939, GneisenauOperator, Kriegsmarine]
-
A.
PrussianCommander
Indicates that an individual holds the position or role of a commander within the Prussian military forces.
-
B.
germanCommander
Indicates that the subject serves as a military commander for German forces in relation to the object.
-
C.
PrussianStrength
Indicates a relationship where an entity possesses or exhibits the military, political, or institutional power characteristic of Prussia.
-
D.
roleInBismarckHunt
Indicates that an entity participated in the historical pursuit of the German battleship Bismarck in a specified role or capacity.
-
E.
notableCommanderAxis
Indicates that the subject entity had a notable military commander role or position on the Axis side in a conflict or war.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fba9ddef488190b785d332580650f0 |
completed | May 6, 2026, 8:51 p.m. |
Created at: May 3, 2026, 4:18 p.m.