Triple
T28641960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bregalnica |
E724949
|
entity |
| Predicate | opponentOfSerbia |
P168111
|
FINISHED |
| Object | Bulgarian Army |
—
|
NE NERFINISHED |
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: Bulgarian Army | Statement: [Battle of Bregalnica, opponentOfSerbia, Bulgarian Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentOfSerbia Context triple: [Battle of Bregalnica, opponentOfSerbia, Bulgarian Army]
-
A.
opponentNationality
Indicates that the related entity is the country or nationality of the opponent in a competitive or adversarial context.
-
B.
aimOfSerbia
Indicates that the referenced goal, objective, or intention is held or pursued by Serbia.
-
C.
mainOpponentOfAustria
Indicates that one entity is the primary rival or adversary of Austria in a given context (such as politics, war, or competition).
-
D.
strengthSerbia
Indicates the relative military, political, or economic power or influence associated with Serbia in a given context.
-
E.
opponentInEuro2016Final
Indicates that one entity was the opposing team of the other entity in the final match of the UEFA Euro 2016 tournament.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 4:45 a.m.