Triple

T546438
Position Surface form Disambiguated ID Type / Status
Subject Semitic languages E12741 entity
Predicate hasISOFamilyCode P189 FINISHED
Object sem 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: sem | Statement: [Semitic languages, hasISOFamilyCode, sem]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasISOFamilyCode
Context triple: [Semitic languages, hasISOFamilyCode, sem]
  • A. hasISOCode chosen
    Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
  • B. containsFamily
    Indicates that one entity includes or encompasses members of a particular family group within it.
  • C. belongsToFamily
    Indicates that an entity is a member of, or is associated as part of, a specific family group.
  • D. hasFourLetterCode
    Indicates that an entity is associated with a code consisting of exactly four characters.
  • E. hasIATAcode
    Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
  • 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_69a49334226c81908b0ea1689ef6aa3f completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a498e150e88190b35b1bc7a376ca07 completed March 1, 2026, 7:52 p.m.
PD Predicate disambiguation batch_69a494b957988190bc269e372df2f0b2 completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.