Triple
T30892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturday Night Massacre |
E616
|
entity |
| Predicate | chronologicalOrder |
P1409
|
FINISHED |
| Object | occurred during Watergate scandal |
—
|
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: occurred during Watergate scandal | Statement: [Saturday Night Massacre, chronologicalOrder, occurred during Watergate scandal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalOrder Context triple: [Saturday Night Massacre, chronologicalOrder, occurred during Watergate scandal]
-
A.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
historicalAssessment
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
C.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
D.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
E.
hasHistoricalContext
chosen
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490d80a0819083bf604c1229e903 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486eb01881909241540dda28e1ff |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.