Triple

T18200024
Position Surface form Disambiguated ID Type / Status
Subject Davide E435756 entity
Predicate hasFeminineForm P1613 FINISHED
Object Davida (nonstandard, rare) NE NERFINISHED

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: Davida (nonstandard, rare) | Statement: [Davide, hasFeminineForm, Davida (nonstandard, rare)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Davida (nonstandard, rare)
Context triple: [Davide, hasFeminineForm, Davida (nonstandard, rare)]
  • A. Davida chosen
    Davida is a feminine given name, often considered a variant of David or Davina, used in various cultures.
  • B. Dávid (Slovak)
    Dávid (Slovak) is a Slovak masculine given name equivalent to David, commonly used in Slovakia.
  • C. Davidsz
    Davidsz is a Dutch patronymic name element meaning "son of David," commonly found in historical Dutch names such as that of the painter Jan Davidsz de Heem.
  • D. Davis (given name)
    Davis is a masculine given name of English origin, often considered a variant of David and used both as a first name and a surname.
  • E. Davina (surname)
    Davina is a surname of likely European origin, derived from the given name Davina, which itself is a feminine form of David.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e0d610f88190b4f69b1c433ea6b1 completed April 19, 2026, 2:04 p.m.
Created at: April 10, 2026, 10:31 a.m.