Triple

T19780425
Position Surface form Disambiguated ID Type / Status
Subject D50 E475115 entity
Predicate connectsToTown P60933 FINISHED
Object Korenica 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: Korenica | Statement: [D50, connectsToTown, Korenica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Korenica
Context triple: [D50, connectsToTown, Korenica]
  • A. Korenica chosen
    Korenica is a small town in central Croatia that serves as an administrative and service center near the Plitvice Lakes National Park.
  • B. Koritnica
    Koritnica is a mountain river in northwestern Slovenia known for its scenic gorge and as a left-bank tributary of the Soča (Isonzo) River.
  • C. Kremenica
    Kremenica is a village-level settlement located within the municipality of Barajevo in Serbia.
  • D. Koritno
    Koritno is a settlement in northwestern Slovenia that forms part of the scenic, tourism-focused area around the town of Bled.
  • E. Grbavica
    Grbavica is a neighborhood in Sarajevo, Bosnia and Herzegovina, known for its residential blocks and its association with local football culture.
  • 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_69d8e51a43a08190956bc6df13c91a77 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65382ff308190832800dd60675f7a completed April 20, 2026, 4:25 p.m.
Created at: April 10, 2026, 1:49 p.m.