Triple

T19750717
Position Surface form Disambiguated ID Type / Status
Subject Daraz E474363 entity
Predicate hasLanguageSupport P203 FINISHED
Object Urdu E6054 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: Urdu | Statement: [Daraz, hasLanguageSupport, Urdu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Urdu
Context triple: [Daraz, hasLanguageSupport, Urdu]
  • A. Urdu language chosen
    Urdu is a major South Asian language, written in a Perso-Arabic script and widely used in Pakistan and parts of India in literature, media, and everyday communication.
  • B. Abbottabadi Hindko
    Abbottabadi Hindko is a regional variety of the Hindko language spoken primarily in and around the city of Abbottabad in northern Pakistan.
  • C. Sindhi
    Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
  • D. Saraiki
    Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • E. Balochi
    Balochi is an Iranian language spoken primarily by the Baloch people across Pakistan, Iran, and Afghanistan, with several dialects and a rich oral literary tradition.
  • 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_69d8e51940a0819087bd2996f98da668 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6529875688190952af476aa5be492 completed April 20, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a07b505634481908e84b80e611b3892 completed May 16, 2026, 12:06 a.m.
Created at: April 10, 2026, 1:48 p.m.