Triple
T32899393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumania (historical region) |
E841566
|
entity |
| Predicate | majorInvasion |
P21625
|
FINISHED |
| Object | Mongol invasion of 1237–1241 |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Mongol invasion of 1237–1241 | Statement: [Cumania (historical region), majorInvasion, Mongol invasion of 1237–1241]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorInvasion Context triple: [Cumania (historical region), majorInvasion, Mongol invasion of 1237–1241]
-
A.
plannedInvasionOf
Indicates that one entity has formulated or organized an invasion targeting another entity.
-
B.
majorWar
Indicates a large-scale, intense armed conflict between major powers or involving substantial military forces and widespread impact.
-
C.
majorLiberationOperation
Indicates a large-scale, coordinated military or strategic action aimed at freeing a territory, population, or group from control, occupation, or oppression.
-
D.
wasInvadedBy
chosen
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
E.
majorBelligerent
Indicates that an entity is a primary or principal participant in a conflict, war, or large-scale hostile engagement.
- F. None of above.
Provenance (3 batches)
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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: May 1, 2026, 1:19 a.m.