Triple

T9478215
Position Surface form Disambiguated ID Type / Status
Subject BSL E228567 entity
Predicate relatedTo P37 FINISHED
Object Auslan E228563 NE 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: Auslan | Statement: [BSL, relatedTo, Auslan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Auslan
Context triple: [BSL, relatedTo, Auslan]
  • A. Auslan chosen
    Auslan is the primary sign language used by the Deaf community in Australia, closely related to British and New Zealand Sign Languages.
  • B. Damara language
    The Damara language is a Khoe (Central Khoisan) language spoken primarily by the Damara people of Namibia.
  • C. Kaera language
    The Kaera language is a Papuan language spoken by a small community on Pantar Island in eastern Indonesia.
  • D. Winaray
    Winaray is an Austronesian language spoken primarily in the Eastern Visayas region of the Philippines, particularly in Samar, northern Leyte, and nearby areas.
  • E. Argobba language
    The Argobba language is an endangered Ethiosemitic language spoken by the Argobba people of Ethiopia, closely related to Harari and other languages of the Harar region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca847162c48190b079076c9595513c completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd8014fd0c819093bd15816f3db357 completed April 1, 2026, 8:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69d16122898c8190947a821f69f957cc completed April 4, 2026, 7:06 p.m.
Created at: March 30, 2026, 7:54 p.m.