Triple
T26568455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Battle of Kosovo |
E666755
|
entity |
| Predicate | involvedMilitary |
P39448
|
FINISHED |
| Object | Ottoman 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: Ottoman army | Statement: [Second Battle of Kosovo, involvedMilitary, Ottoman army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedMilitary Context triple: [Second Battle of Kosovo, involvedMilitary, Ottoman army]
-
A.
involvesMilitaryService
Indicates that the relationship or situation includes participation in, obligation to, or association with formal military service.
-
B.
militaryIssue
Indicates that one entity formally provides or distributes military-related items, orders, or directives to another entity.
-
C.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
D.
armedForcesInvolved
chosen
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
E.
involvesMilitaryChange
Indicates that the situation or event includes a modification, reorganization, or shift in military forces, structures, capabilities, or operations.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 1:56 a.m.