Triple

T20413237
Position Surface form Disambiguated ID Type / Status
Subject Jumong E500641 entity
Predicate associatedWith P37 FINISHED
Object Jolbon 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: Jolbon | Statement: [Jumong, associatedWith, Jolbon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jolbon
Context triple: [Jumong, associatedWith, Jolbon]
  • A. Jolbon chosen
    Jolbon was an early capital city of the ancient Korean kingdom of Goguryeo, associated with its founding period and initial royal seat.
  • B. Jelbi
    Jelbi is a mobility app by Berlin’s public transport operator that integrates various transport options like buses, trains, bikes, and scooters into a single platform for planning and booking trips.
  • C. Jabonga
    Jabonga is a coastal municipality in the province of Agusan del Norte in the Caraga region of Mindanao, Philippines.
  • D. Jalonke
    Jalonke is a Mande language spoken primarily in Guinea and neighboring West African countries by the Jalonke (Yalunka) people.
  • E. Jebali
    Jebali is a Tunisian surname most notably associated with politician and former Prime Minister Hamadi Jebali.
  • 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_69e0b4a935588190b9446a99b37ced44 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67a417f208190be9bc11650ee0a87 completed April 20, 2026, 7:10 p.m.
Created at: April 16, 2026, 11:30 a.m.