Triple
T25779695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosnian Croat leadership |
E649252
|
entity |
| Predicate | laterInConflictWith |
P4897
|
FINISHED |
| Object | Bosniak leadership |
—
|
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: Bosniak leadership | Statement: [Bosnian Croat leadership, laterInConflictWith, Bosniak leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterInConflictWith Context triple: [Bosnian Croat leadership, laterInConflictWith, Bosniak leadership]
-
A.
dateConflict
Indicates that two scheduled dates or time periods overlap or otherwise cannot both be accommodated without a clash.
-
B.
conflictWith
chosen
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
C.
recurringConflictWith
Indicates a relationship in which two entities experience conflicts or disputes that occur repeatedly over time.
-
D.
eventInConflict
Indicates that an event occurs within, is part of, or is directly associated with a specific conflict.
-
E.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 22, 2026, 5:37 a.m.