Triple

T14933988
Position Surface form Disambiguated ID Type / Status
Subject Ishkashimi E372341 entity
Predicate countryStatusInAfghanistan P16670 FINISHED
Object minority language 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: minority language | Statement: [Ishkashimi, countryStatusInAfghanistan, minority language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: countryStatusInAfghanistan
Context triple: [Ishkashimi, countryStatusInAfghanistan, minority language]
  • A. statusInAfghanistan chosen
    Indicates the condition, role, or legal standing an entity holds within the context of Afghanistan.
  • B. countryStatus
    Indicates the political or legal condition of a country, such as its sovereignty, recognition, or current state in international or domestic contexts.
  • C. countrySpecificStatus
    Indicates a status or condition that is defined or applied specifically in the context of a particular country.
  • D. countryResponse
    Indicates that a country issues, provides, or expresses a reply, reaction, or stance in response to a particular event, request, or situation.
  • E. statusInPakistan
    Indicates the legal, social, or operational condition or standing that something or someone has within the context of Pakistan.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded646a0808190ba5c0c91bde011c5 completed April 15, 2026, 12:05 a.m.
PD Predicate disambiguation batch_69de9a52ba988190a26e268b4ea083ea completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:37 a.m.