Triple
T31849950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muye |
E813038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient battlefield |
C2871
|
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 battlefield Context triple: [Muye, instanceOf, ancient battlefield]
-
A.
historic battlefield
chosen
A historic battlefield is a geographically defined site where significant military engagements occurred, preserved or recognized for its cultural, educational, and commemorative value.
-
B.
Bronze Age battle
A Bronze Age battle is an armed conflict between organized groups during the Bronze Age, typically involving bronze weapons, chariots, early fortifications, and tactics shaped by emerging complex societies.
-
C.
legendary battlefield
A legendary battlefield is a historically or mythically renowned site where a pivotal, large-scale conflict occurred, leaving lasting cultural, strategic, or symbolic significance.
-
D.
ancient Near Eastern war
Ancient Near Eastern war encompasses the organized, often ritualized conflicts between early civilizations of Mesopotamia, Egypt, Anatolia, and the Levant, characterized by chariot warfare, fortified cities, imperial expansion, and the intertwining of military action with religion and kingship.
-
E.
ancient place
An ancient place is a historically significant location from antiquity, often associated with early civilizations, archaeological remains, or long-standing cultural traditions.
- 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.