Triple

T26859320
Position Surface form Disambiguated ID Type / Status
Subject Elliot E676282 entity
Predicate hasSpellingVariantFrequency P176706 FINISHED
Object less common than Elliott 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: less common than Elliott | Statement: [Elliot, hasSpellingVariantFrequency, less common than Elliott]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSpellingVariantFrequency
Context triple: [Elliot, hasSpellingVariantFrequency, less common than Elliott]
  • A. hasVariantSpelling
    Indicates that one term is an alternative spelling form of another term.
  • B. spellingVariantPattern
    Indicates a relationship where one form of a word is a systematic spelling variant of another, following a recognizable pattern of orthographic change.
  • C. hasLinguisticVariety
    Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
  • D. linguisticVariant
    Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
  • E. hasSpellingWithAccent
    Indicates that one form of a word or name is spelled using accented characters compared to another form.
  • 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_69eee9b9d7708190a15d7485709ae981 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f6e6029a10819098ff21f58079e70e completed May 3, 2026, 6:06 a.m.
PD Predicate disambiguation batch_69f6e3d5e8188190b1e1c2e5d1b77031 completed May 3, 2026, 5:57 a.m.
PDg Predicate description generation batch_69f6e60109648190947a64ca4ce81a3a completed May 3, 2026, 6:06 a.m.
Created at: April 27, 2026, 5:23 a.m.