Triple

T443824
Position Surface form Disambiguated ID Type / Status
Subject Sinhala E10172 entity
Predicate hasRegisterDistinction P13255 FINISHED
Object formal vs colloquial registers 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: formal vs colloquial registers | Statement: [Sinhala, hasRegisterDistinction, formal vs colloquial registers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegisterDistinction
Context triple: [Sinhala, hasRegisterDistinction, formal vs colloquial registers]
  • A. hasDistinction
    Indicates that one entity possesses, is awarded, or is recognized with a special honor, title, or mark of excellence in relation to another entity or context.
  • B. hasRegister
    Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
  • C. uniformDistinction
    Indicates that a clear and consistent difference is maintained between two or more entities within a given context.
  • D. hasGenderDistinction
    Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
  • E. hasStandardRegister
    Indicates that something is expressed or occurs in a standard, neutral, or non-marked linguistic register.
  • 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_69a2e8465ef481909655c681b01e2986 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2ef43e8f88190a5d368add11a38c0 completed Feb. 28, 2026, 1:36 p.m.
PD Predicate disambiguation batch_69a2edde2b9c8190bd20b582eb4c5065 completed Feb. 28, 2026, 1:30 p.m.
PDg Predicate description generation batch_69a2eeb9e6b0819093863959a6e5730a completed Feb. 28, 2026, 1:33 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.