Triple
T30361710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeanie Deans |
E772304
|
entity |
| Predicate | setAgainstHistoricalEvent |
P169114
|
FINISHED |
| Object | Porteous Riots |
—
|
NE NERFINISHED |
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: Porteous Riots | Statement: [Jeanie Deans, setAgainstHistoricalEvent, Porteous Riots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setAgainstHistoricalEvent Context triple: [Jeanie Deans, setAgainstHistoricalEvent, Porteous Riots]
-
A.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
historicallyOpposedBy
Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
-
C.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
D.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
-
E.
isHistoricNameOfEventAt
Indicates that a given historic name refers to or was used for a specific event that occurred at a particular place or time.
- F. None of above. chosen
Provenance (4 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68243b5d8819092d8a0a1261f5fb2 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 7:58 p.m.