Triple
T33088612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirpitz risk theory |
E846710
|
entity |
| Predicate | targetedAdversary |
P196509
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Tirpitz risk theory, targetedAdversary, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedAdversary Context triple: [Tirpitz risk theory, targetedAdversary, United Kingdom]
-
A.
commonAdversary
Indicates that two or more entities share the same opponent, rival, or threat.
-
B.
targetOfThreat
Indicates that one entity is the recipient or intended victim of a threat made by another entity.
-
C.
targetedBecauseOf
Indicates that one entity is made a target of an action, harm, or scrutiny specifically due to possessing a particular attribute, identity, or characteristic.
-
D.
targetedForce
Indicates a deliberate application of force directed at a specific target or entity.
-
E.
otherAdversary
Indicates that one entity is an adversary of another, distinct from any primary or previously identified adversary.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: May 1, 2026, 1:26 a.m.