Triple
T3479756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Kiev (1240) |
E73460
|
entity |
| Predicate | chronologyWithinCampaign |
P26528
|
FINISHED |
| Object | occurred after Mongol campaigns against other Rus' principalities |
—
|
LITERAL FINISHED |
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: occurred after Mongol campaigns against other Rus' principalities | Statement: [Siege of Kiev (1240), chronologyWithinCampaign, occurred after Mongol campaigns against other Rus' principalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyWithinCampaign Context triple: [Siege of Kiev (1240), chronologyWithinCampaign, occurred after Mongol campaigns against other Rus' principalities]
-
A.
chronologyWithinConflict
chosen
Indicates that one event or time period occurs within the temporal span of a specified conflict or war.
-
B.
chronologicallyCovers
Indicates that one time period, event, or sequence extends over and includes the entire chronological span of another.
-
C.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
D.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
E.
involvesChronology
Indicates that the relationship or action explicitly depends on, references, or organizes events according to their order or position in time.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb7461708190898002fbd1191f34 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.