Triple

T22934334
Position Surface form Disambiguated ID Type / Status
Subject Laiyolo E569536 entity
Predicate hasAlternativeName P39 FINISHED
Object Laiolo 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: Laiolo | Statement: [Laiyolo, hasAlternativeName, Laiolo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laiolo
Context triple: [Laiyolo, hasAlternativeName, Laiolo]
  • A. Laiolo chosen
    Laiolo is an alternate name for the Laiyolo language, an Austronesian language spoken in parts of Indonesia.
  • B. Looma
    Looma is an alternative name for Loma, which may refer to various places, peoples, or entities sharing that designation.
  • C. Liluah
    Liluah is a suburban locality in the Howrah district of West Bengal, India, known for its residential areas and railway facilities near Kolkata.
  • D. Leola
    Leola is a small unincorporated community in Lancaster County, Pennsylvania, known for its rural character and proximity to Amish farmlands.
  • E. Lalolara
    Lalolara are a subgroup of the Tolaki people, an indigenous ethnic community of Southeast Sulawesi, Indonesia, with their own distinct cultural and social traditions.
  • 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_69e24590862c8190858f180ad302adab completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18134484c8190b7311606c17d058d completed April 29, 2026, 3:55 a.m.
Created at: April 17, 2026, 3:44 p.m.