Triple

T14895986
Position Surface form Disambiguated ID Type / Status
Subject Olonets Karelian E359876 entity
Predicate closelyRelatedTo P37 FINISHED
Object Ludic Karelian E72966 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: Ludic Karelian | Statement: [Olonets Karelian, closelyRelatedTo, Ludic Karelian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ludic Karelian
Context triple: [Olonets Karelian, closelyRelatedTo, Ludic Karelian]
  • A. Kuron
    Kuron is an alternative name for the Kulon language, a lesser-known Austronesian language of Indonesia.
  • B. Lalkurti
    Lalkurti is a historic residential and commercial neighborhood in Rawalpindi, Pakistan, known for its colonial-era origins and proximity to the city’s main cantonment area.
  • C. Meänkieli
    Meänkieli is a Finnic minority language closely related to Finnish, traditionally spoken by the Tornedalian people in northern Sweden.
  • D. Karelian language chosen
    The Karelian language is a Uralic language closely related to Finnish, traditionally spoken by the Karelian people in parts of Finland and northwestern Russia.
  • E. Kodava language
    Kodava language is a Dravidian language spoken primarily by the Kodava (Coorg) community in the Kodagu district of Karnataka, India.
  • 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_69d827980cbc8190a0c569ae3940a1d9 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69ded6070b248190be8f4f91a0c0b1f3 completed April 15, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe6b679fb081908cf8f41acfba3b99 completed May 8, 2026, 11:01 p.m.
Created at: April 10, 2026, 2:10 a.m.