Triple

T25684983
Position Surface form Disambiguated ID Type / Status
Subject Eastern Boro E644041 entity
Predicate hasRelationToStandard P61209 FINISHED
Object dialect of Boro 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: dialect of Boro | Statement: [Eastern Boro, hasRelationToStandard, dialect of Boro]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRelationToStandard
Context triple: [Eastern Boro, hasRelationToStandard, dialect of Boro]
  • A. hasAssociatedStandard
    Indicates that something is linked to or governed by a particular standard or set of standards.
  • B. standardizationRelation
    Indicates a relationship in which one entity defines, enforces, or aligns with a common standard, norm, or specification used by another entity.
  • C. associatedWithStandard
    Indicates that something is linked or connected to a specific standard, such as being defined, governed, or guided by that standard.
  • D. hasStandardLanguageRelation chosen
    Indicates that there exists a standardized linguistic relationship between two entities, such as one being the standard or reference language form for the other.
  • E. isStandardOf
    Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
  • 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_69e77e8046888190b07ffa58c7e2c37a completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69fba78aca4c8190b8f1831e8cc04e06 completed May 6, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69fba34a65a4819088bac6c17542d71c completed May 6, 2026, 8:23 p.m.
Created at: April 21, 2026, 8:06 p.m.