Triple

T6400267
Position Surface form Disambiguated ID Type / Status
Subject Ivasayen Ivatan E144043 entity
Predicate hasNameInEnglish P3437 FINISHED
Object Ivasayen Ivatan E144043 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: Ivasayen Ivatan | Statement: [Ivasayen Ivatan, hasNameInEnglish, Ivasayen Ivatan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ivasayen Ivatan
Context triple: [Ivasayen Ivatan, hasNameInEnglish, Ivasayen Ivatan]
  • A. Ivasayen Ivatan chosen
    Ivasayen Ivatan is a variety of the Ivatan language spoken by the Ivatan people of the Batanes Islands in the northern Philippines.
  • B. Saribas Iban
    Saribas Iban is a regional dialect of the Iban language traditionally spoken by Iban communities in the Saribas area of Sarawak, Malaysia.
  • C. Umiray Agta
    Umiray Agta is an indigenous Negrito group in the Philippines known for its distinct culture and language, closely related to the Umiray Dumaget language.
  • D. Yakan
    Yakan is an Austronesian language spoken primarily by the Yakan people of Basilan and nearby areas in the southern Philippines.
  • E. Kawayan
    Kawayan is a coastal municipality on Biliran Island in the Eastern Visayas region of the Philippines.
  • 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_69c008dc56fc81908d43ffcc11d73bdd completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c068994354819086cd51b661137f5a completed March 22, 2026, 10:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6389fe9608190adc68f3ad5b0471a completed March 27, 2026, 7:58 a.m.
Created at: March 22, 2026, 4:35 p.m.