Triple

T8380057
Position Surface form Disambiguated ID Type / Status
Subject Carian language E197664 entity
Predicate relatedTo P37 FINISHED
Object Milyan language E722283 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: Milyan language | Statement: [Carian language, relatedTo, Milyan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Milyan language
Context triple: [Carian language, relatedTo, Milyan language]
  • A. Milyan language chosen
    The Milyan language is an extinct Anatolian Indo-European language once spoken in southwestern Asia Minor, known primarily from a small corpus of inscriptions closely related to Lycian.
  • B. Mon language
    Mon language is an Austroasiatic language historically spoken in parts of Myanmar and Thailand, notable for its ancient literary tradition and influence on regional scripts and cultures.
  • C. Miluk language
    The Miluk language is an extinct Native American language once spoken by the Coos people along the southern Oregon coast.
  • D. Mina language
    The Mina language is a Gbe language of the Niger-Congo family spoken primarily in Togo and neighboring West African regions.
  • E. Mam language
    Mam language is a Mayan language spoken primarily by the Mam people in the highland regions of Guatemala and parts of southern Mexico.
  • 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_69ca82f64c188190af4e1608036b865d completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb80c57080819097eef2b7e46eaaee completed March 31, 2026, 8:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69cde803ac088190ae185ef444c9c7b9 completed April 2, 2026, 3:52 a.m.
Created at: March 30, 2026, 6:02 p.m.