Triple

T8866075
Position Surface form Disambiguated ID Type / Status
Subject Chaldiot E211020 entity
Predicate linguisticDomain P17147 FINISHED
Object phonology LITERAL 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: phonology | Statement: [Chaldiot, linguisticDomain, phonology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: linguisticDomain
Context triple: [Chaldiot, linguisticDomain, phonology]
  • A. hasLinguisticDomain chosen
    Indicates that something (such as a term, expression, or resource) is associated with or applies within a particular linguistic domain or language context.
  • B. linguisticField
    Indicates that something pertains to or is associated with a particular area or subdiscipline within linguistics.
  • C. linguisticScope
    Indicates the range or domain within language (such as a phrase, clause, or discourse segment) over which a particular linguistic element, feature, or operation has effect.
  • D. linguisticType
    Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
  • E. linguisticArea
    Indicates a regional context in which languages share features due to geographic proximity and contact rather than common genetic origin.
  • F. None of above.

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_69ca838d3c7c8190a849566d5afd2b11 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6106d41081909db710bda8aaf6fd completed April 1, 2026, 12:04 a.m.
PD Predicate disambiguation batch_69cc5c279ea481908c71756f694b66bf completed March 31, 2026, 11:43 p.m.
Created at: March 30, 2026, 6:51 p.m.