Triple
T31849980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhou forces |
E813039
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Chinese army |
C33709
|
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: ancient Chinese army Context triple: [Zhou forces, instanceOf, ancient Chinese army]
-
A.
Han dynasty commandery
A Han dynasty commandery was an administrative division governed by a centrally appointed commandery governor, responsible for civil administration, tax collection, and local security within a defined territorial region of the Han Empire.
-
B.
ancient Chinese bronze
An ancient Chinese bronze is a ritual or utilitarian object cast from bronze alloys in early Chinese civilizations, often richly decorated and used for ceremonial, religious, or status-related purposes.
-
C.
legendary army
chosen
A legendary army is a renowned military force whose extraordinary prowess, historic victories, and enduring reputation elevate it to near-mythic status in collective memory.
-
D.
ancient Chinese city
An ancient Chinese city is a fortified urban center that served as a political, economic, military, and cultural hub, characterized by planned layouts, defensive walls, gates, palaces, temples, markets, and residential quarters reflecting traditional Chinese cosmology and social hierarchy.
-
E.
ancient Chinese culture
Ancient Chinese culture encompasses the philosophies, social structures, artistic traditions, religious beliefs, and technological innovations that developed in China from its earliest dynasties through imperial times, profoundly shaping East Asian civilization.
- F. None of above.
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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:51 p.m.