Triple
T25946487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | territory of Bosnia and Herzegovina |
E653850
|
entity |
| Predicate | hasWarLegacy |
P88059
|
FINISHED |
| Object | Bosnian War |
—
|
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: Bosnian War | Statement: [territory of Bosnia and Herzegovina, hasWarLegacy, Bosnian War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWarLegacy Context triple: [territory of Bosnia and Herzegovina, hasWarLegacy, Bosnian War]
-
A.
warLegacy
chosen
Indicates that a past war has left lasting impacts or consequences on an entity, such as social, political, economic, or cultural effects that persist over time.
-
B.
hasNotableWar
Indicates that an entity is associated with a significant or historically important war.
-
C.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
-
D.
hasFictionalWar
Indicates that there exists a fictional or imagined war involving the related entities.
-
E.
hasModernLegacyIn
Indicates that something continues to exert influence, relevance, or impact within a modern context, domain, or location.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 22, 2026, 8:43 a.m.