Triple
T19788123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Srebrenica |
E475331
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Potočari |
—
|
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: Potočari | Statement: [Srebrenica, near, Potočari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Potočari Context triple: [Srebrenica, near, Potočari]
-
A.
Potočari
chosen
Potočari is a village in eastern Bosnia and Herzegovina known as the site of the Srebrenica genocide and the location of the Srebrenica–Potočari Memorial and Cemetery.
-
B.
Omišalj
Omišalj is a historic coastal town and tourist destination on the northern part of the Croatian island of Krk, overlooking the Kvarner Gulf.
-
C.
Brodnica
Brodnica is a historic town in north-central Poland known for its medieval architecture and location on the Drwęca River.
-
D.
Stolac
Stolac is a historic town in southern Bosnia and Herzegovina known for its rich cultural heritage, Ottoman-era architecture, and nearby medieval necropolises.
-
E.
Dedinje
Dedinje is an affluent residential neighborhood in Belgrade, Serbia, known for its villas, diplomatic residences, and prominent landmarks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 10, 2026, 1:49 p.m.