Triple
T14979669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nika riots |
E373540
|
entity |
| Predicate | hasKeyBattleOrAction |
P1703
|
FINISHED |
| Object | massacre in the Hippodrome |
—
|
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: massacre in the Hippodrome | Statement: [Nika riots, hasKeyBattleOrAction, massacre in the Hippodrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyBattleOrAction Context triple: [Nika riots, hasKeyBattleOrAction, massacre in the Hippodrome]
-
A.
hasKeyBattle
chosen
Indicates that an entity is associated with a major or decisive battle that is central to its history, role, or significance.
-
B.
hasKeyAction
Indicates that an entity performs or is associated with a primary or essential action within a given context.
-
C.
hasKeyActivity
Indicates that an entity is associated with or performs a primary or central activity.
-
D.
hasKeyActor
Indicates that an entity plays a primary or central role (a key actor) in relation to another entity or context.
-
E.
hasKeyMovement
Indicates that one entity possesses or defines the primary or characteristic movement pattern associated with another entity.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6fcebf481909f72cab577560d82 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:51 a.m.