Triple
T833031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Bogside |
E18008
|
entity |
| Predicate | chronologicalSuccessor |
P78
|
FINISHED |
| Object | wider August 1969 Northern Ireland riots |
—
|
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: wider August 1969 Northern Ireland riots | Statement: [Battle of the Bogside, chronologicalSuccessor, wider August 1969 Northern Ireland riots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalSuccessor Context triple: [Battle of the Bogside, chronologicalSuccessor, wider August 1969 Northern Ireland riots]
-
A.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
B.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
C.
eventualSuccessor
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
D.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
E.
successor
chosen
Indicates that one entity directly follows another in an ordered sequence or position.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb647988190950e1790bcfa60a5 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.