Triple
T28560315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kumanovo |
E722519
|
entity |
| Predicate | aimOfOttomanEmpire |
P109222
|
FINISHED |
| Object | to halt Serbian advance into Macedonia |
—
|
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: to halt Serbian advance into Macedonia | Statement: [Battle of Kumanovo, aimOfOttomanEmpire, to halt Serbian advance into Macedonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimOfOttomanEmpire Context triple: [Battle of Kumanovo, aimOfOttomanEmpire, to halt Serbian advance into Macedonia]
-
A.
strategicObjectiveOttoman
Indicates that one entity serves as or relates to a strategic objective or goal specifically concerning the Ottoman Empire.
-
B.
primaryTacticOttomans
Indicates the main military or strategic method predominantly employed by the Ottoman forces in a given conflict or context.
-
C.
OttomanDynasty
Indicates a dynastic or ruling-family relationship associated with the Ottoman Empire.
-
D.
aimOfByzantines
Indicates the goal or objective pursued by the Byzantines in a given context.
-
E.
primaryObjectiveOfEmpire
chosen
Indicates the main strategic goal or overarching purpose that an empire seeks to achieve or maintain.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:04 a.m.