Triple
T8032002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinggan League |
E187006
|
entity |
| Predicate | hasCountyLevelDivision |
P747
|
FINISHED |
| Object | Arxan |
E708418
|
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: Arxan | Statement: [Hinggan League, hasCountyLevelDivision, Arxan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arxan Context triple: [Hinggan League, hasCountyLevelDivision, Arxan]
-
A.
Arxan
chosen
Arxan is a county-level city in the Hinggan League of Inner Mongolia, China, known for its forested landscapes, volcanic landforms, and hot springs.
-
B.
Arakhin
Arakhin is a tractate of the Mishnah and Talmud that deals primarily with the laws of vows of valuation and consecration to the Temple.
-
C.
Arlanxeo
Arlanxeo is a global synthetic rubber company specializing in high-performance elastomer products for the automotive, construction, and industrial sectors.
-
D.
Akurgal
Akurgal is a Turkish surname most notably associated with the prominent archaeologist Ekrem Akurgal.
-
E.
Aru
Aru is a group of closely related Austronesian languages spoken primarily in the Aru Islands of eastern Indonesia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ef18da48190835454a5eb969da7 |
completed | March 31, 2026, 3:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc63c911c081909751b614966d986c |
completed | April 1, 2026, 12:16 a.m. |
Created at: March 30, 2026, 5:22 p.m.