Triple
T9190928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussians |
E220585
|
entity |
| Predicate | notableUprisingPeriod |
P4699
|
FINISHED |
| Object | 1260–1274 Prussian uprisings |
—
|
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: 1260–1274 Prussian uprisings | Statement: [Prussians, notableUprisingPeriod, 1260–1274 Prussian uprisings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUprisingPeriod Context triple: [Prussians, notableUprisingPeriod, 1260–1274 Prussian uprisings]
-
A.
notableRevolt
Indicates a significant uprising or rebellion in which the subject played an important or historically notable role.
-
B.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
C.
uprisingDate
chosen
Indicates the date on which an uprising or rebellion occurred or began.
-
D.
notableProtest
Indicates that an entity is recognized for having led, organized, or been centrally involved in a significant protest or demonstration.
-
E.
uprising
Indicates a collective act of resistance or rebellion by a group against an established authority or ruling power.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5bf25c081909e651b67ef8ecc33 |
completed | April 1, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.