Triple

T27326471
Position Surface form Disambiguated ID Type / Status
Subject Hans Weber E689662 entity
Predicate etymologyOfGivenName P64332 FINISHED
Object short form of Johannes 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: short form of Johannes | Statement: [Hans Weber, etymologyOfGivenName, short form of Johannes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: etymologyOfGivenName
Context triple: [Hans Weber, etymologyOfGivenName, short form of Johannes]
  • A. nameEtymologyFor chosen
    Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
  • B. hasNameEtymologyIn
    Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
  • C. possibleNameEtymology
    Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
  • D. etymologyReason
    Indicates the reason, source, or origin explaining how or why a term acquired its particular etymology.
  • E. etymologyContext
    Indicates the contextual or situational background (such as time, place, culture, or domain) relevant to the origin and historical development of a word or term.
  • 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_69ef355d4cb08190ab032c0a2e7d3753 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f627edd6d08190a059d44edecfb368 completed May 2, 2026, 4:35 p.m.
PD Predicate disambiguation batch_69f620e4b1c88190a17940251abc68fd completed May 2, 2026, 4:05 p.m.
Created at: April 27, 2026, 11:36 a.m.