Triple
T1730921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sedgemoor |
E37807
|
entity |
| Predicate | notableAftermath |
P1706
|
FINISHED |
| Object | Bloody Assizes conducted by Judge Jeffreys |
—
|
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: Bloody Assizes conducted by Judge Jeffreys | Statement: [Battle of Sedgemoor, notableAftermath, Bloody Assizes conducted by Judge Jeffreys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAftermath Context triple: [Battle of Sedgemoor, notableAftermath, Bloody Assizes conducted by Judge Jeffreys]
-
A.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
B.
notableOutcome
chosen
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableRevival
Indicates that something has undergone a significant or noteworthy revival, resurgence, or renewed prominence after a period of decline or inactivity.
-
E.
notableAbsence
Indicates that something or someone is conspicuously missing from a context where their presence would normally be expected or significant.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.