Triple

T21833674
Position Surface form Disambiguated ID Type / Status
Subject Lavukaleve language E539063 entity
Predicate hasAlternativeName P39 FINISHED
Object Lavukaleve 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: Lavukaleve | Statement: [Lavukaleve language, hasAlternativeName, Lavukaleve]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lavukaleve
Context triple: [Lavukaleve language, hasAlternativeName, Lavukaleve]
  • A. Lavukaleve chosen
    Lavukaleve is an indigenous Papuan language spoken in the Russell Islands of the Solomon Islands.
  • B. Lohavan
    Lohavan is a sacred forest region within the Vraja Mandala pilgrimage area associated with the pastimes of Lord Krishna in Hindu tradition.
  • C. Alatala
    Alatala is a settlement located within the Qakh District of Azerbaijan.
  • D. Labungkari
    Labungkari is a town in Indonesia’s Southeast Sulawesi province, known as an administrative and local economic center in the region.
  • E. Larajasse
    Larajasse is a rural commune in eastern France situated within the scenic Monts du Lyonnais range, known for its hilly landscapes and agricultural character.
  • 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_69e0c475cda88190987d08f23caebdc1 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0a7a5eeb88190b58b5b6d363cd6e3 completed April 28, 2026, 12:27 p.m.
Created at: April 16, 2026, 6:55 p.m.