Triple

T23280004
Position Surface form Disambiguated ID Type / Status
Subject Puyuma language E588831 entity
Predicate hasAlternativeName P39 FINISHED
Object Beinan 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: Beinan | Statement: [Puyuma language, hasAlternativeName, Beinan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beinan
Context triple: [Puyuma language, hasAlternativeName, Beinan]
  • A. Beinan chosen
    Beinan is an alternative name for the Puyuma language, an Austronesian language spoken by the Puyuma indigenous people of southeastern Taiwan.
  • B. An Bien
    An Bien is a coastal rural district-level town in Vietnam’s Kien Giang Province, known for its agriculture and fishing-based economy in the Mekong Delta region.
  • C. Balla
    Balla is an Italian surname most notably associated with Giacomo Balla, a leading painter of the Futurist movement.
  • D. Bain
    Bain is a variant form of the name or term "Bean," used as an alternative spelling or version in certain contexts.
  • E. Baçaim
    Baçaim is the former Portuguese name for Bassein (now Vasai), a historic coastal town and former colonial stronghold near Mumbai in the Indian state of Maharashtra.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e25d16e2c08190a291de254703129e completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196419eac819081d0beb5767046dc completed April 29, 2026, 5:25 a.m.
Created at: April 17, 2026, 4:50 p.m.