Triple
T34672291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Decimation |
E890406
|
entity |
| Predicate | reversedByEvent |
P124237
|
FINISHED |
| Object | The Blip (restoration event) |
—
|
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: The Blip (restoration event) | Statement: [The Decimation, reversedByEvent, The Blip (restoration event)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reversedByEvent Context triple: [The Decimation, reversedByEvent, The Blip (restoration event)]
-
A.
reversedChangeOf
Indicates that one entity represents the inverse or opposite direction of a change or transformation described by another entity.
-
B.
repealedAfterEvent
Indicates that a law or regulation was repealed as a consequence of, or following, a specific event.
-
C.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
D.
overturnedByEvent
chosen
Indicates that a prior decision, state, or outcome is reversed or nullified as a result of a specific event.
-
E.
reversedByCharacter
Indicates that one character undoes, inverts, or turns around an action, effect, or state that was previously established by another character.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7232166488190939c02bdaeacb490 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.