Triple
T1013096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarajevo |
E21865
|
entity |
| Predicate | wasBesiegedIn |
P11070
|
FINISHED |
| Object | 1992–1996 |
—
|
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: 1992–1996 | Statement: [Sarajevo, wasBesiegedIn, 1992–1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBesiegedIn Context triple: [Sarajevo, wasBesiegedIn, 1992–1996]
-
A.
isSiegeOf
chosen
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
B.
wasInvadedBy
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
C.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
D.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
E.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7be907c8190b5c6ea89257755a7 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b72207c08190a3dbb2aa7acbbc71 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.