Triple

T17174430
Position Surface form Disambiguated ID Type / Status
Subject Wekerom E416820 entity
Predicate hasRegionCode P3446 FINISHED
Object GE E129065 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: GE | Statement: [Wekerom, hasRegionCode, GE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GE
Context triple: [Wekerom, hasRegionCode, GE]
  • A. GE
    GE is the ISO 3166-1 alpha-2 country code for Georgia, a nation at the crossroads of Eastern Europe and Western Asia.
  • B. GE
    GE is the commonly used abbreviation for Global Entry, a U.S. government program that provides expedited clearance for pre-approved, low-risk international travelers entering the United States.
  • C. GE chosen
    GE is the Swiss canton code for Geneva, a major city and canton in western Switzerland known for its international organizations and financial center.
  • D. GE
    GE is the abbreviation for ICANN’s Government Engagement function, which manages and coordinates ICANN’s relationships and interactions with governments and intergovernmental organizations worldwide.
  • E. GM
    GM is the station code used to identify GMA Kamuning station in the Manila Metro Rail Transit system.
  • 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_69d886d5f34c8190b24564dfaa63f3fb completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3fc0c329081909f118bd4b7be8653 completed April 18, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0148435f6081909bfc6cc1ef59d971 completed May 11, 2026, 3:08 a.m.
Created at: April 10, 2026, 5:37 a.m.