Triple
T33430913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action of 22 September 1914 |
E856127
|
entity |
| Predicate | countryOfAttackingSubmarine |
P202761
|
FINISHED |
| Object | German Empire |
—
|
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: German Empire | Statement: [Action of 22 September 1914, countryOfAttackingSubmarine, German Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfAttackingSubmarine Context triple: [Action of 22 September 1914, countryOfAttackingSubmarine, German Empire]
-
A.
sunkCountry
Indicates that one entity (typically a vessel or force) caused the sinking of a country’s ship(s) or naval assets belonging to another country.
-
B.
countryOfShipSunk
Indicates the country to which a ship that was sunk belonged or was registered.
-
C.
countryAttacked
Indicates that one country has carried out an attack against another country.
-
D.
locationOfTorpedoAttack
Indicates the place where a torpedo attack occurred or was carried out.
-
E.
attackCountry
Indicates that one country initiates a hostile or military action against another country.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00b6199c348190b1e90375f737d026 |
completed | May 10, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a00b5169a7881909a07167c4188731f |
completed | May 10, 2026, 4:40 p.m. |
| PDg | Predicate description generation | batch_6a00b618cb10819095ccef12d8e303c5 |
completed | May 10, 2026, 4:45 p.m. |
Created at: May 1, 2026, 1:36 a.m.