Triple

T20628590
Position Surface form Disambiguated ID Type / Status
Subject Ivo E506886 entity
Predicate relatedName P3889 FINISHED
Object Iwo 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: Iwo | Statement: [Ivo, relatedName, Iwo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Iwo
Context triple: [Ivo, relatedName, Iwo]
  • A. Iwo chosen
    Iwo is a prominent city in southwestern Nigeria known for its historical significance and cultural heritage within Osun State.
  • B. Sulfur Island
    Sulfur Island is the English translation of the Japanese name for Iwo Jima, a small volcanic island in the Pacific Ocean known for a major World War II battle.
  • C. Guadalcanal
    Guadalcanal is a major island in the Solomon Islands best known as the site of a pivotal World War II campaign between Allied and Japanese forces in the Pacific.
  • D. Kuto Bay
    Kuto Bay is a picturesque white-sand bay on New Caledonia’s Île des Pins, known for its calm turquoise waters and popularity as a swimming and cruise-ship stop.
  • E. Savo Island
    Savo Island is a small volcanic island in the Solomon Islands, known for its active volcano, hot springs, and historical significance in World War II naval battles.
  • 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_69e0b4bd4a0081908d4e97a590a33fb2 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6abe771e88190a48471bf83b4804d completed April 20, 2026, 10:42 p.m.
Created at: April 16, 2026, 11:42 a.m.