Triple

T5958852
Position Surface form Disambiguated ID Type / Status
Subject Kotor region E132583 entity
Predicate contains P35 FINISHED
Object Morinj E482949 NE 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: Morinj | Statement: [Kotor region, contains, Morinj]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Morinj
Context triple: [Kotor region, contains, Morinj]
  • A. Morinj chosen
    Morinj is a small coastal village in Montenegro known for its scenic setting along the Bay of Kotor and its tranquil beaches.
  • B. Brunico
    Brunico is a historic town and popular tourist center in northern Italy’s Alps, known for its medieval old town, castle, and proximity to the Dolomites.
  • C. Gherdëina
    Gherdëina is a Ladin dialect spoken in the Val Gardena region of the Dolomites in northern Italy.
  • D. Ampezzo
    Ampezzo is a town in the Dolomite region of northern Italy known for its Ladin cultural and linguistic heritage.
  • E. Savogna d’Isonzo
    Savogna d’Isonzo is a small municipality in northeastern Italy, near the border with Slovenia, known for its bilingual Italian-Slovene community and proximity to the Isonzo (Soča) River.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c0086c2364819091e9fe2f58fa2517 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c039c48d0c81908e794c52fddf2ca2 completed March 22, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0e3e3736c8190b445156f0c1bdf1f completed March 23, 2026, 6:55 a.m.
Created at: March 22, 2026, 4:02 p.m.