Triple

T9192375
Position Surface form Disambiguated ID Type / Status
Subject Aslian branch E220620 entity
Predicate hasLanguage P15 FINISHED
Object Temiar E730587 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: Temiar | Statement: [Aslian branch, hasLanguage, Temiar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Temiar
Context triple: [Aslian branch, hasLanguage, Temiar]
  • A. Temiar chosen
    The Temiar are an indigenous Orang Asli group of Peninsular Malaysia known for their forest-based lifestyle, rich animist traditions, and distinctive ritual music and dance.
  • B. Tialo
    Tialo is an Austronesian language of the Tomini–Tolitoli subgroup spoken in Central Sulawesi, Indonesia.
  • C. The Turim
    The Turim is a foundational 14th-century Jewish legal code by Rabbi Jacob ben Asher that systematically organizes halakhic rulings into four major sections.
  • D. Tianeti
    Tianeti is a small town and administrative center in eastern Georgia, situated in the mountainous Mtskheta-Mtianeti region.
  • E. Taygi
    Taygi is a lesser-known Samoyedic language of the Uralic family traditionally spoken by an indigenous group in northern Siberia.
  • 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_69ca83e7ba70819088b74866d9da2c30 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd5c077b4819086c74e91ee4bd75e completed April 1, 2026, 8:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69d077797be081908300a5baa0041ce5 completed April 4, 2026, 2:29 a.m.
Created at: March 30, 2026, 7:24 p.m.