Triple

T2559882
Position Surface form Disambiguated ID Type / Status
Subject Svan language E57216 entity
Predicate closelyRelatedTo P37 FINISHED
Object Laz language E207514 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: Laz language | Statement: [Svan language, closelyRelatedTo, Laz language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laz language
Context triple: [Svan language, closelyRelatedTo, Laz language]
  • A. Laz language chosen
    The Laz language is a South Caucasian (Kartvelian) minority language spoken mainly along the Black Sea coast of Turkey and Georgia.
  • B. Lasalimu language
    The Lasalimu language is an Austronesian language spoken by a small community on Buton Island in Southeast Sulawesi, Indonesia.
  • C. Lakalai language
    The Lakalai language is an Austronesian language spoken by the Lakalai people of New Britain in Papua New Guinea.
  • D. Logba language
    The Logba language is a Niger-Congo language spoken by the Logba people of southeastern Ghana.
  • E. Zabana language
    The Zabana language is an Oceanic language spoken primarily on Santa Isabel Island in the Solomon Islands.
  • 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_69ab4a4ef9008190a0e6d4422b9418b7 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd333370c8190b1d64ec99e999913 completed March 7, 2026, 7:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69af655f72fc81908a85a69f95d0b827 completed March 10, 2026, 12:27 a.m.
Created at: March 6, 2026, 9:48 p.m.