Triple
T8239036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Przemyśl |
E192483
|
entity |
| Predicate | tacticsUsedByDefenders |
P13663
|
FINISHED |
| Object | sorties against Russian siege lines |
—
|
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: sorties against Russian siege lines | Statement: [Siege of Przemyśl, tacticsUsedByDefenders, sorties against Russian siege lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticsUsedByDefenders Context triple: [Siege of Przemyśl, tacticsUsedByDefenders, sorties against Russian siege lines]
-
A.
defensiveTactics
chosen
Indicates the use or implementation of strategies, maneuvers, or methods intended to protect, guard, or defend against threats or attacks.
-
B.
hasCommonTacticOfOpponents
Indicates that two or more entities share the same tactic or strategy used by their respective opponents.
-
C.
defensiveStructure
Indicates a relationship where one entity functions as a structure built or used to protect, defend, or fortify another entity or area.
-
D.
objectiveOfDefenders
Indicates that a particular goal, task, or purpose is assigned to or pursued by the defenders in a given context.
-
E.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783a8cf48190bf85394fd3bd79e2 |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.