Triple

T21519439
Position Surface form Disambiguated ID Type / Status
Subject Emperor Juntoku E530933 entity
Predicate deathPlace P21 FINISHED
Object Sado Province
Sado Province was a historical Japanese province located on Sado Island in the Sea of Japan, known for its exile of political figures and its rich gold and silver mines.
E2297197 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: Sado Province | Statement: [Emperor Juntoku, deathPlace, Sado Province]
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: Sado Province
Triple: [Emperor Juntoku, deathPlace, Sado Province]
Generated description
Sado Province was a historical Japanese province located on Sado Island in the Sea of Japan, known for its exile of political figures and its rich gold and silver mines.

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_69e0c45d95a081908e7962ad215da746 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee884af0f08190bc1f3d70e57a325d completed April 26, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a832cb2d5ac81908fdf76751020afcc completed Aug. 17, 2026, 3:45 p.m.
NEDg Description generation batch_6a832d1e57088190982b823a34cc926d completed Aug. 17, 2026, 3:47 p.m.
NED2 Entity disambiguation (via description) batch_6a832daee24c81908bacccd6f4d54571 completed Aug. 17, 2026, 3:50 p.m.
Created at: April 16, 2026, 6:26 p.m.