Triple
T6542982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoa Lu Ancient Capital |
E168334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic capital of Vietnam |
C21552
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic capital of Vietnam Context triple: [Hoa Lu Ancient Capital, instanceOf, historic capital of Vietnam]
-
A.
historical province of Vietnam
A historical province of Vietnam is a former administrative region that existed under past Vietnamese dynasties or colonial regimes, whose boundaries, governance, and status have since been reorganized or dissolved in the modern provincial system.
-
B.
city in Vietnam
A city in Vietnam is an urban administrative unit characterized by a dense population, developed infrastructure, and a concentration of economic, cultural, and governmental activities within the Vietnamese national context.
-
C.
district of Hanoi
A district of Hanoi is an administrative subdivision of Vietnam's capital city, typically encompassing multiple wards or communes and serving as a local governance unit for urban planning, public services, and community administration.
-
D.
region of Vietnam
A region of Vietnam is a large geographic and cultural area within the country, typically defined by shared historical, economic, and environmental characteristics that distinguish it from other parts of Vietnam.
-
E.
province of Vietnam
A province of Vietnam is a first-level administrative division governed by a provincial government under the central authority of the Vietnamese state, encompassing multiple districts, towns, and cities.
- F. None of above. chosen
Provenance (1 batch)
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_69c68a51564081909e93aee0dbd9cca3 |
completed | March 27, 2026, 1:46 p.m. |
Created at: March 27, 2026, 1:50 p.m.