Triple

T29072143
Position Surface form Disambiguated ID Type / Status
Subject Dirk Coster E735837 entity
Predicate hasElementNamedContext P150492 FINISHED
Object hafnium named after Hafnia (Latin name for Copenhagen) 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: hafnium named after Hafnia (Latin name for Copenhagen) | Statement: [Dirk Coster, hasElementNamedContext, hafnium named after Hafnia (Latin name for Copenhagen)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasElementNamedContext
Context triple: [Dirk Coster, hasElementNamedContext, hafnium named after Hafnia (Latin name for Copenhagen)]
  • A. hasNameElementType
    Indicates that something includes a specific type or category of element within its name.
  • B. hasComponentGivenName
    Indicates that an entity includes a component whose specific given (first) name is the value of the predicate.
  • C. hasProperNameElement chosen
    Indicates that an entity’s proper name includes a specific component (such as a word, phrase, or segment) as one of its constituent elements.
  • D. hasCurrentNameContext
    Indicates that an entity is associated with the name it currently uses or is recognized by in the present context.
  • E. hasElementType
    Indicates that something is composed of or contains elements that are of a specified type.
  • 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_69f077e9b0a48190bb79548279cb7f64 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f6b903538481909cffcb6cc1cc0e70 completed May 3, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69f6b626120c819097c9ad04487570d7 completed May 3, 2026, 2:42 a.m.
Created at: April 28, 2026, 10:20 a.m.