Triple
T22741597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunhua |
E562427
|
entity |
| Predicate | borderingAdministrativeUnit |
P224
|
FINISHED |
| Object | Helong |
—
|
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: Helong | Statement: [Dunhua, borderingAdministrativeUnit, Helong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Helong Context triple: [Dunhua, borderingAdministrativeUnit, Helong]
-
A.
Helong
chosen
Helong is a county-level city in northeastern China's Jilin Province, known for its significant ethnic Korean population and role within the Yanbian Korean Autonomous Prefecture.
-
B.
Helong
The Helong are an indigenous ethnic group of western Timor known for their distinct Austronesian language and traditional coastal and island communities.
-
C.
Yanbian
Yanbian is an autonomous prefecture in northeastern China's Jilin Province, known for its significant ethnic Korean population and cultural ties to the Korean Peninsula.
-
D.
Zhanshan
Zhanshan is a Chinese given name that can be borne by individuals such as Zhu Zhanshan.
-
E.
Houhai
Houhai is a coastal area in Shenzhen, China, known for its modern waterfront developments, shopping centers, and vibrant nightlife.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1797400fc8190bec26726f434f787 |
completed | April 29, 2026, 3:22 a.m. |
Created at: April 17, 2026, 3:23 p.m.