Triple

T21051096
Position Surface form Disambiguated ID Type / Status
Subject Javed E518583 entity
Predicate instanceOf P0 FINISHED
Object Persian-language masculine given name C4308 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: Persian-language masculine given name
Context triple: [Javed, instanceOf, Persian-language masculine given name]
  • A. Persian given name chosen
    A Persian given name is a personal name of Iranian origin, often derived from the Persian language, history, literature, or cultural and religious traditions, used to identify an individual.
  • B. Arabic-language masculine patronymic
    An Arabic-language masculine patronymic is a personal name component that identifies a man as the son or descendant of a specific male ancestor, typically formed with elements like "ibn" or "bin" followed by the father's given name.
  • C. Persian-language surname
    A Persian-language surname is a family name originating from the Persian language and cultural tradition, often reflecting ancestry, geography, occupation, or personal attributes.
  • D. masculine given name
    A masculine given name is a personal name traditionally assigned to individuals identified as male, often reflecting cultural, historical, or familial significance.
  • E. Arabic given name
    An Arabic given name is a personal name of Arabic linguistic and cultural origin, often derived from religious, historical, or meaningful lexical roots and typically used as a first name in Arabic-speaking and Islamic societies.
  • F. None of above.

Provenance (1 batch)

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_69e0b5053ac48190921529544959e906 completed April 16, 2026, 10:08 a.m.
Created at: April 16, 2026, 2:35 p.m.