Triple

T21786575
Position Surface form Disambiguated ID Type / Status
Subject Radimlja necropolis E537852 entity
Predicate locatedNear P294 FINISHED
Object Stolac 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: Stolac | Statement: [Radimlja necropolis, locatedNear, Stolac]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stolac
Context triple: [Radimlja necropolis, locatedNear, Stolac]
  • A. Stolac chosen
    Stolac is a historic town in southern Bosnia and Herzegovina known for its rich cultural heritage, Ottoman-era architecture, and nearby medieval necropolises.
  • B. Gradačac
    Gradačac is a historic town and municipality in northern Bosnia and Herzegovina, known for its Ottoman-era fortress and role as a regional cultural center.
  • C. Dedinje
    Dedinje is an affluent residential neighborhood in Belgrade, Serbia, known for its villas, diplomatic residences, and prominent landmarks.
  • D. 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.
  • E. Vreoci
    Vreoci is a suburban settlement in the Lazarevac municipality of Belgrade, Serbia, known for its proximity to major lignite coal mining operations.
  • 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_69e0c47198f881908cb0d237266c10e9 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0621b5d6881908b74bc999c94fa3d completed April 28, 2026, 7:30 a.m.
Created at: April 16, 2026, 6:52 p.m.