Triple

T19765732
Position Surface form Disambiguated ID Type / Status
Subject Corinne E474749 entity
Predicate hasRelatedName P3889 FINISHED
Object Coreen 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: Coreen | Statement: [Corinne, hasRelatedName, Coreen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Coreen
Context triple: [Corinne, hasRelatedName, Coreen]
  • A. Coreen chosen
    Coreen is a rural locality within the Urana Shire local government area in New South Wales, Australia.
  • B. Taegwan
    Taegwan is a town and county-level city in North Pyongan Province in northwestern North Korea.
  • C. Yeon
    Yeon is the given name of King Seonjo, a Joseon dynasty monarch who ruled Korea during the late 16th century, including the period of the Japanese invasions.
  • D. Ko Ri
    Ko Ri is one of the small islands that make up Thailand’s Surin Islands archipelago in the Andaman Sea.
  • E. Hyesan
    Hyesan is a major city in northern North Korea, located on the border with China along the Yalu River and serving as an important regional administrative and transport hub.
  • 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_69d8e51a43a08190956bc6df13c91a77 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e653226af081909992ff5568bb54a5 completed April 20, 2026, 4:24 p.m.
Created at: April 10, 2026, 1:48 p.m.