Triple

T31463166
Position Surface form Disambiguated ID Type / Status
Subject Northern dialect of Auslan E802657 entity
Predicate superordinateLanguage P96709 FINISHED
Object Auslan 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: Auslan | Statement: [Northern dialect of Auslan, superordinateLanguage, Auslan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: superordinateLanguage
Context triple: [Northern dialect of Auslan, superordinateLanguage, Auslan]
  • A. hasSuperordinateLanguage chosen
    Indicates that one language serves as a higher-level, overarching, or more general language in relation to another language.
  • B. standardLanguageOf
    Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
  • C. canonicalLanguage
    Indicates that one entity is the officially recognized or standard language associated with another entity.
  • D. governingLanguage
    Indicates the language that holds official or authoritative status over a given entity, such as a region, organization, or document.
  • E. macrolanguageOf
    Indicates that one language functions as a macrolanguage encompassing or grouping together one or more related individual languages.
  • 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_69f348c84c1c81908739f100ecf7394e completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f7c777e924819081a6634f549fe552 completed May 3, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69f7c475c58c8190a883554231e88c88 completed May 3, 2026, 9:56 p.m.
Created at: April 30, 2026, 9:21 p.m.