Triple

T6674694
Position Surface form Disambiguated ID Type / Status
Subject Roviana language E151820 entity
Predicate hasAlternativeName P39 FINISHED
Object Rubiana E529786 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: Rubiana | Statement: [Roviana language, hasAlternativeName, Rubiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rubiana
Context triple: [Roviana language, hasAlternativeName, Rubiana]
  • A. Rubiana chosen
    Rubiana is an alternative name for Roviana, a language and cultural region of the Solomon Islands in the western Pacific.
  • B. Suriana
    Suriana is a small genus of tropical coastal shrubs in the flowering plant order Fabales, best known for the species Suriana maritima that inhabits sandy seashores.
  • C. Yehenara
    Yehenara was a prominent Manchu noble clan of the Qing dynasty, best known as the family of Empress Dowager Cixi.
  • D. Luciana
    Luciana is a feminine given name of Latin origin, commonly used in Spanish- and Portuguese-speaking countries.
  • E. Sheyla
    Sheyla is a feminine given name, typically considered a variant of Sheila or Shayla and used in various cultures.
  • 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_69c687f830bc81909eb8b04dbb8450b1 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b0f1d9d081909670f5c0b7389c0d completed March 27, 2026, 4:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6f7a30b7481908c36ff9035f62731 completed March 27, 2026, 9:33 p.m.
Created at: March 27, 2026, 2:03 p.m.