Triple

T176474
Position Surface form Disambiguated ID Type / Status
Subject Punjabi language E3585 entity
Predicate writingSystemOrigin P454 FINISHED
Object Gurmukhi derived from Landa scripts 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: Gurmukhi derived from Landa scripts | Statement: [Punjabi language, writingSystemOrigin, Gurmukhi derived from Landa scripts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: writingSystemOrigin
Context triple: [Punjabi language, writingSystemOrigin, Gurmukhi derived from Landa scripts]
  • A. writingSystem chosen
    Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
  • B. isMostWidelyUsedWritingSystem
    Indicates that the subject writing system is used by more people or in more contexts than any other writing system.
  • C. replacedWritingSystem
    Indicates that one writing system has been superseded or taken the place of another as the primary script used for a language or context.
  • D. hasLanguageOfOrigin
    Indicates that one entity has its origin or source in the language specified by another entity.
  • E. hasOfficialOrthography
    Indicates that an entity has a formally recognized and standardized system for writing its language or name.
  • 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_69a25374990081909766d30c79a18e0e completed Feb. 28, 2026, 2:31 a.m.
NER Named-entity recognition batch_69a258fd278481908ad4498e03f38e2f completed Feb. 28, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69a25669d99481908c5e82ba8641205a completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:39 a.m.