Triple
T2663299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukla Pass |
E54773
|
entity |
| Predicate | battleObjective |
P38518
|
FINISHED |
| Object | liberation of Slovakia |
—
|
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: liberation of Slovakia | Statement: [Dukla Pass, battleObjective, liberation of Slovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleObjective Context triple: [Dukla Pass, battleObjective, liberation of Slovakia]
-
A.
ConfederateObjective
Indicates that an action or plan is aimed at achieving a goal or objective of the Confederate side in a conflict or war.
-
B.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
C.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
-
D.
UnionObjective
Indicates that an entity has the goal, purpose, or objective of forming, maintaining, or advancing a union or unified organization.
-
E.
objectiveOfAttackers
chosen
Indicates the target or goal that attackers aim to reach or affect through their attack.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd96b9f1c8190a8a9460ca88a9aaf |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.