Triple
T22120302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normandy–Flanders alliance |
E546647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 11th-century alliance |
C24628
|
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: 11th-century alliance Context triple: [Normandy–Flanders alliance, instanceOf, 11th-century alliance]
-
A.
historical alliance
chosen
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural goals.
-
B.
Catholic military alliance
A Catholic military alliance is a coalition of armed forces from predominantly Catholic states or groups, formed to defend shared religious, political, or territorial interests under a common Catholic identity.
-
C.
11th-century ruler
An 11th-century ruler is a sovereign or political leader who held authority over a territory during the 1000s CE, navigating feudal structures, religious influences, and emerging state formations of the medieval world.
-
D.
13th-century conflict
A 13th-century conflict is a military or political struggle that occurred between 1201 and 1300, shaped by medieval feudal structures, religious motivations, and emerging state powers.
-
E.
early modern political alliance
An early modern political alliance is a formal or informal agreement between states, dynasties, or political entities from roughly the 15th to 18th centuries to cooperate for mutual security, territorial, economic, or dynastic advantage within a shifting balance-of-power system.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.