Triple
T2328941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Warsaw (1939) |
E48355
|
entity |
| Predicate | aimOfAttacker |
P38945
|
FINISHED |
| Object | capture of Polish capital |
—
|
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: capture of Polish capital | Statement: [Siege of Warsaw (1939), aimOfAttacker, capture of Polish capital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfAttacker Context triple: [Siege of Warsaw (1939), aimOfAttacker, capture of Polish capital]
-
A.
attacker
Indicates a relationship where one entity initiates a harmful or hostile action against another entity.
-
B.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
-
C.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
D.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
E.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcc2fa25c8190858c1c541b914f4c |
completed | March 7, 2026, 6:56 a.m. |
Created at: March 4, 2026, 7:50 p.m.