Triple

T4222715
Position Surface form Disambiguated ID Type / Status
Subject SENĆOŦEN E94378 entity
Predicate hasOrthographyDeveloper P55404 FINISHED
Object W̱SÁNEĆ community members 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: W̱SÁNEĆ community members | Statement: [SENĆOŦEN, hasOrthographyDeveloper, W̱SÁNEĆ community members]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOrthographyDeveloper
Context triple: [SENĆOŦEN, hasOrthographyDeveloper, W̱SÁNEĆ community members]
  • A. hasOfficialOrthography
    Indicates that an entity has a formally recognized and standardized system for writing its language or name.
  • B. hasOrthographicReform
    Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
  • C. hasDistinctOrthographyFrom
    Indicates that two written forms are orthographically different from each other, even if they may represent the same or related linguistic content.
  • D. hasStandardOrthographySince
    Indicates that a language or writing system has used a particular standardized orthography starting from a specified point in time.
  • E. usesStandardOrthographyOf
    Indicates that one entity writes or represents language according to the standard orthographic system defined for another entity.
  • 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_69b3451997e08190851db4a9a588837d completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b34e4bf6088190926b982039a12079 completed March 12, 2026, 11:37 p.m.
PD Predicate disambiguation batch_69b347f1d7b48190bd8974c03c7dc937 completed March 12, 2026, 11:10 p.m.
PDg Predicate description generation batch_69b34e4ace648190acf911853d4fcf86 completed March 12, 2026, 11:37 p.m.
Created at: March 12, 2026, 11:04 p.m.