Triple

T32084720
Position Surface form Disambiguated ID Type / Status
Subject Baoting Li and Miao Autonomous County E819407 entity
Predicate hasChineseName P4878 FINISHED
Object 保亭黎族苗族自治县
保亭黎族苗族自治县 is an autonomous county in southern Hainan, China, known for its Li and Miao ethnic minority communities and tropical mountainous landscapes.
E1991253 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: 保亭黎族苗族自治县 | Statement: [Baoting Li and Miao Autonomous County, hasChineseName, 保亭黎族苗族自治县]
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: 保亭黎族苗族自治县
Triple: [Baoting Li and Miao Autonomous County, hasChineseName, 保亭黎族苗族自治县]
Generated description
保亭黎族苗族自治县 is an autonomous county in southern Hainan, China, known for its Li and Miao ethnic minority communities and tropical mountainous landscapes.

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_69f348ff8ef88190931c08ba530a36bc completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b5881a4081908bb27068841a1fea completed May 3, 2026, 2:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2eddf16f7481908611310497a8f3e5 completed June 14, 2026, 4:59 p.m.
NEDg Description generation batch_6a2ede8d1d748190ac4f0ed7ac37ba90 completed June 14, 2026, 5:02 p.m.
NED2 Entity disambiguation (via description) batch_6a2edf31c5048190b590db0fe6181ccb completed June 14, 2026, 5:04 p.m.
Created at: May 1, 2026, 12:24 a.m.