Triple

T3991436
Position Surface form Disambiguated ID Type / Status
Subject Occitan language E86997 entity
Predicate hasISO6393Code P8719 FINISHED
Object oci E86997 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: oci | Statement: [Occitan language, hasISO6393Code, oci]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: oci
Context triple: [Occitan language, hasISO6393Code, oci]
  • A. oci chosen
    oci is the ISO 639-2 code for Occitan, a Romance language spoken primarily in southern France and parts of Italy and Spain.
  • B. OC
    OC is the post-nominal designation for Officer of the Order of Canada, one of the country’s highest civilian honors recognizing outstanding achievement and service.
  • C. ulos
    Ulos is a handwoven ceremonial textile central to Batak culture in North Sumatra, Indonesia, symbolizing blessings, social status, and kinship ties.
  • D. gon
    gon is the ISO 639-3 code for the Gondi language, a Dravidian language spoken by the Gond people in central India.
  • E. ofs
    ofs is the ISO 639-3 language code for Old Frisian, a historical West Germanic language once spoken in parts of the coastal Netherlands and Germany.
  • 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_69aed94118148190975e6aa4e554cde9 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefa02ed6881908e31d342413fed26 completed March 9, 2026, 4:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69b54035e92c81909dc2be18719b062c completed March 14, 2026, 11:02 a.m.
Created at: March 9, 2026, 3:33 p.m.