Triple
T37775913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mojkovac |
E941686
|
entity |
| Predicate | hasCommanderForMontenegro |
P180048
|
FINISHED |
| Object | Janko Vukotić |
E2283574
|
NE 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: Janko Vukotić | Statement: [Battle of Mojkovac, hasCommanderForMontenegro, Janko Vukotić]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommanderForMontenegro Context triple: [Battle of Mojkovac, hasCommanderForMontenegro, Janko Vukotić]
-
A.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
B.
commanderForBulgaria
Indicates that an entity serves or has served in the role of commander on behalf of, or in the service of, Bulgaria.
-
C.
commanderForPiedmontSardinia
Indicates that one entity served as a military commander on behalf of, or in the service of, the state of Piedmont-Sardinia.
-
D.
commanderForSardinia
Indicates that one entity serves as the military or naval commander responsible for Sardinia.
-
E.
commanderCountry
chosen
Indicates that a person serving as a commander is associated with or represents a specific country in that commanding role.
- F. None of above.
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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4266225c9c8190abd2f0f00e8de299 |
completed | June 29, 2026, 12:33 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.