Triple
T16546403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Grochów |
E401952
|
entity |
| Predicate | aimOfPolishSide |
P123999
|
FINISHED |
| Object | defend approaches to Warsaw |
—
|
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: defend approaches to Warsaw | Statement: [Battle of Grochów, aimOfPolishSide, defend approaches to Warsaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfPolishSide Context triple: [Battle of Grochów, aimOfPolishSide, defend approaches to Warsaw]
-
A.
objectivePoland
Indicates that something has Poland as its goal, target, or intended destination.
-
B.
PolishObjective
Indicates that an entity is the target or goal of a polishing action or process.
-
C.
PolishUnit
Indicates that a unit is associated with Poland, typically by nationality, origin, or affiliation.
-
D.
aimOfOtherSide
Indicates that one party’s goal or intended outcome is directed toward or defined in relation to the opposing or counterpart side in a relationship or interaction.
-
E.
PolishCommander
Indicates that an entity serves as a military commander associated with Poland.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fbe3fb48190bad143b50dc73c7e |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.