Triple

T21093852
Position Surface form Disambiguated ID Type / Status
Subject Karpf E519707 entity
Predicate hasOriginNote P16050 FINISHED
Object likely a variant of the surname Karp 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: likely a variant of the surname Karp | Statement: [Karpf, hasOriginNote, likely a variant of the surname Karp]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOriginNote
Context triple: [Karpf, hasOriginNote, likely a variant of the surname Karp]
  • A. originNote chosen
    Indicates a note or comment that explains the origin, source, or provenance of an entity or relationship.
  • B. hasNotabilityOrigin
    Indicates that an entity’s notability or prominence arises from, or is primarily associated with, a specified origin (such as a place, context, or source).
  • C. hasOriginIn
    Indicates that something begins, arises, or is derived from a specified source, place, or cause.
  • D. isNotedOn
    Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
  • E. hasAuthorOfNoteFor
    Indicates that one entity is recognized as the noteworthy or cited author associated with a particular note, annotation, or commentary on another entity.
  • 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_69e0b507dd9081908fb8bfcbef4c8b46 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e709517a18819081ede1d38e2c4391 completed April 21, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69e5dbfcd5e881908f1e4e0d2d237856 completed April 20, 2026, 7:55 a.m.
Created at: April 16, 2026, 2:51 p.m.