Triple

T31746985
Position Surface form Disambiguated ID Type / Status
Subject Bosville E810296 entity
Predicate hasOrthographicVariantRelation P33995 FINISHED
Object Boswell NE NERFINISHED

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: Boswell | Statement: [Bosville, hasOrthographicVariantRelation, Boswell]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOrthographicVariantRelation
Context triple: [Bosville, hasOrthographicVariantRelation, Boswell]
  • A. orthographicVariant chosen
    Indicates that two written forms are different spellings or orthographic representations of the same linguistic item.
  • B. hasOrthographicReform
    Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
  • C. hasOrthographicConvention
    Indicates that there is a specific writing or spelling convention that governs how something is represented in written form.
  • D. hasDistinctOrthographyFrom
    Indicates that two written forms are orthographically different from each other, even if they may represent the same or related linguistic content.
  • E. hasOrthographyStatus
    Indicates the orthographic status or condition of how something is written or spelled, such as its conformity to a particular writing system or standard.
  • 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_69f348e233cc819083b6695f70cd75d8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fd82ed2a4c81908bd7797fbd2e3d08 completed May 8, 2026, 6:30 a.m.
PD Predicate disambiguation batch_69fd814cc10481908e4f8123d35a5d0c completed May 8, 2026, 6:23 a.m.
Created at: April 30, 2026, 11:27 p.m.