Triple

T22467018
Position Surface form Disambiguated ID Type / Status
Subject Candidasa E555381 entity
Predicate near P350 FINISHED
Object Amed 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: Amed | Statement: [Candidasa, near, Amed]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amed
Context triple: [Candidasa, near, Amed]
  • A. Amed
    Amed is the historical name of the city now known as Diyarbakır, a major cultural and political center in southeastern Turkey, especially significant for Kurdish heritage.
  • B. Amed chosen
    Amed is a coastal fishing village and popular diving and snorkeling destination in eastern Bali, Indonesia, known for its black sand beaches and coral reefs.
  • C. Amden
    Amden is a Swiss mountain village and municipality in the canton of St. Gallen, known for its scenic location above Lake Walen and its hiking and skiing opportunities.
  • D. Ameide
    Ameide is a small historic town in the Dutch province of South Holland, known for its location along the Lek River and traditional Dutch architecture.
  • E. Amares
    Amares is a municipality in northern Portugal known for its rural landscapes, historical churches, and proximity to the city of Braga in the Minho region.
  • 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_69e11e51fdec8190adfdf9f8a6362221 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15b84e4a88190b6fbfdbd754ba1c5 completed April 29, 2026, 1:14 a.m.
Created at: April 16, 2026, 8:48 p.m.