Triple

T13427788
Position Surface form Disambiguated ID Type / Status
Subject Seri people E313528 entity
Predicate hasEthnonym P1435 FINISHED
Object Seri E83371 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: Seri | Statement: [Seri people, hasEthnonym, Seri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seri
Context triple: [Seri people, hasEthnonym, Seri]
  • A. Seri chosen
    The Seri are an Indigenous people of northwestern Mexico, traditionally living along the Gulf of California coast and known for their rich maritime culture, distinctive language, and artisanal crafts.
  • B. Seria
    Seria is an oil-producing coastal town in Brunei known as one of the country’s main petroleum hubs and the site of key historical events.
  • C. Seri Rama
    Seri Rama is the Malay literary adaptation of the Hindu epic hero Rama, depicted as a virtuous prince and central figure in the traditional narrative Hikayat Seri Rama.
  • D. Ser.
    Ser. is the standard Latin abbreviation for the praenomen Servius, commonly used in ancient Roman naming conventions.
  • E. Series S
    Series S is a set of ITU-T telecommunications standards focused on telegraph and related terminal equipment specifications.
  • 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_69d806ad0c44819088833ae1ec9e9690 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaed1f9208190bf5ef5b8a7ded376 completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f730883cb48190add9469c48dc3e89 completed May 3, 2026, 11:24 a.m.
Created at: April 9, 2026, 9:40 p.m.