Triple
T19788165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Žepa |
E475332
|
entity |
| Predicate | UNStatusDuringBosnianWar |
P19322
|
FINISHED |
| Object | UN-declared safe area |
—
|
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: UN-declared safe area | Statement: [Žepa, UNStatusDuringBosnianWar, UN-declared safe area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNStatusDuringBosnianWar Context triple: [Žepa, UNStatusDuringBosnianWar, UN-declared safe area]
-
A.
outcomeOfCampaignsAgainstSerbia
Indicates the result or consequences produced by specific military or political campaigns directed against Serbia.
-
B.
laterStanceOnYugoslavia
Indicates a subject’s subsequent or revised position, opinion, or policy stance regarding Yugoslavia at a later point in time.
-
C.
statusDuringWar
chosen
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
D.
stanceOnYugoslavia
Indicates a subject’s position, attitude, or policy toward Yugoslavia as a political or historical entity.
-
E.
statusInCroatia
Indicates the legal, social, or official standing or condition that an entity holds within the context of Croatia.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65389c9ac81909e61b3cbb9213e72 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.