Triple

T15208230
Position Surface form Disambiguated ID Type / Status
Subject Lomaiviti group E363444 entity
Predicate hasMainIsland P756 FINISHED
Object Koro E1143115 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: Koro | Statement: [Lomaiviti group, hasMainIsland, Koro]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koro
Context triple: [Lomaiviti group, hasMainIsland, Koro]
  • A. Koro chosen
    Koro is a volcanic island in Fiji’s Lomaiviti archipelago, known for its rugged terrain, traditional villages, and surrounding coral reefs.
  • B. Koro Uma
    Koro Uma is an alternate name for the Uma language, an Austronesian language spoken in Central Sulawesi, Indonesia.
  • C. Koro Wachi
    Koro Wachi is a lesser-known Plateau language spoken in central Nigeria, notable for its place within the Benue–Congo branch of the Niger–Congo language family.
  • D. Kogarah
    Kogarah is a suburb in southern Sydney, New South Wales, Australia, known as a residential and commercial hub in the St George area.
  • E. Rakau
    Rakau is a small rural settlement in Belarus located near the historical hill of Dziaržynskaja Hara, the country’s highest point.
  • 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e006b8e2788190bd1831762e4181ae completed April 15, 2026, 9:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69fedd2f86688190bafdfe72033eda90 completed May 9, 2026, 7:07 a.m.
Created at: April 10, 2026, 3:11 a.m.