Triple
T14276876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Could-Have-Been King and his army of Meanwhiles and Neverweres |
E353938
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary 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: legendary army Context triple: [the Could-Have-Been King and his army of Meanwhiles and Neverweres, instanceOf, legendary army]
-
A.
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.
-
B.
warlord army
A warlord army is a militarized force loyal to a single powerful leader, often operating outside formal state control and sustained through conquest, coercion, and resource extraction.
-
C.
armoured army
An armoured army is a military force primarily composed of heavily protected, mechanized units such as tanks and armored vehicles designed for high-mobility, high-impact ground warfare.
-
D.
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.
-
E.
royal army
A royal army is a formally organized, state-sanctioned military force that serves, protects, and enforces the authority and interests of a monarchy.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.