Triple
T11294589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birger Eriksen |
E267417
|
entity |
| Predicate | effectOfAction |
P53074
|
FINISHED |
| Object | sinking of Blücher in the Oslofjord |
—
|
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: sinking of Blücher in the Oslofjord | Statement: [Birger Eriksen, effectOfAction, sinking of Blücher in the Oslofjord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOfAction Context triple: [Birger Eriksen, effectOfAction, sinking of Blücher in the Oslofjord]
-
A.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
B.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
C.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
D.
predictedEffect
Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
-
E.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e98b149481909f432a6b9ef8bfbb |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.