Triple

T35411584
Position Surface form Disambiguated ID Type / Status
Subject King of Goryeo E1023525 entity
Predicate titleHolder P1911 FINISHED
Object Gojong of Goryeo
Gojong of Goryeo was a 13th-century Korean monarch who ruled during the Mongol invasions and oversaw Goryeo’s eventual subordination to the Yuan dynasty.
E2164792 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: Gojong of Goryeo | Statement: [King of Goryeo, titleHolder, Gojong of Goryeo]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Gojong of Goryeo
Triple: [King of Goryeo, titleHolder, Gojong of Goryeo]
Generated description
Gojong of Goryeo was a 13th-century Korean monarch who ruled during the Mongol invasions and oversaw Goryeo’s eventual subordination to the Yuan dynasty.

Provenance (5 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_69f76df54bac8190bd0d3b0eb35cda5f completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f795672b40819087ccce744e044124 completed May 3, 2026, 6:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38bfbc5cf08190bbf748a66cbea028 completed June 22, 2026, 4:53 a.m.
NEDg Description generation batch_6a38c0545cd8819082a2f7906b911b2d completed June 22, 2026, 4:55 a.m.
NED2 Entity disambiguation (via description) batch_6a38c0c09b188190843fdf263b9074fb completed June 22, 2026, 4:57 a.m.
Created at: May 3, 2026, 4:03 p.m.