Triple

T7007705
Position Surface form Disambiguated ID Type / Status
Subject Abdullah bin Hassan Al Nuaimi E162498 entity
Predicate hasPatronymicName P7966 FINISHED
Object bin Hassan 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: bin Hassan | Statement: [Abdullah bin Hassan Al Nuaimi, hasPatronymicName, bin Hassan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPatronymicName
Context triple: [Abdullah bin Hassan Al Nuaimi, hasPatronymicName, bin Hassan]
  • A. hasPatronymicUse
    Indicates that an entity uses a patronymic form of naming derived from a parent’s (typically the father’s) given name.
  • B. hasPatronymicLine
    Indicates a genealogical relationship where one entity’s name or lineage is derived from the father’s given name, forming a patronymic line.
  • C. isPatronymicSurname
    Indicates that a surname is derived from the given name of a father or male ancestor, typically signifying "son/daughter of" that person.
  • D. patronymicName chosen
    Indicates that one entity’s name is derived from or based on the given name of a parent or ancestor, typically the father.
  • E. isMatronymicOf
    Indicates that one entity is a name or designation derived from the mother of another entity, typically used as that entity’s family or identifying 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_69c6885928148190ae31909fbb5e9849 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dc36e3fc8190957445132a9ffb5f completed March 27, 2026, 7:36 p.m.
PD Predicate disambiguation batch_69c6d7c67c94819084fdcf0398606027 completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:33 p.m.