Triple

T15641584
Position Surface form Disambiguated ID Type / Status
Subject Pitman (namesake unknown) E376078 entity
Predicate hasUnknownFamilyName P119573 FINISHED
Object true 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: true | Statement: [Pitman (namesake unknown), hasUnknownFamilyName, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUnknownFamilyName
Context triple: [Pitman (namesake unknown), hasUnknownFamilyName, true]
  • A. hasUnknownGivenName
    Indicates that the given (first) name of the entity is not known or not specified.
  • B. hasFamilyNameOf
    Indicates that one entity bears or uses the same family name (surname) as another entity.
  • C. hasNameInFamily
    Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
  • D. hasFamilyNameOfOwner
    Indicates that an entity has an owner whose family (last) name is the specified value.
  • E. hasFamilyNameElement
    Indicates that an entity has a specific component or segment that forms part of its family name.
  • F. None of above. chosen

Provenance (4 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_69d85cd035a48190b73d5579ab73969a completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ed23d688190bea996f90989d406 completed April 16, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69deda890140819082608931e993dd61 completed April 15, 2026, 12:23 a.m.
PDg Predicate description generation batch_69dff7f3016c8190ac68d76e65e07af4 completed April 15, 2026, 8:41 p.m.
Created at: April 10, 2026, 4:15 a.m.