Triple
T20391581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgment Day (Terminator) |
E498097
|
entity |
| Predicate | goalOfProtagonists |
P42284
|
FINISHED |
| Object | prevent Judgment Day |
—
|
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: prevent Judgment Day | Statement: [Judgment Day (Terminator), goalOfProtagonists, prevent Judgment Day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfProtagonists Context triple: [Judgment Day (Terminator), goalOfProtagonists, prevent Judgment Day]
-
A.
characterMotivation
Indicates the underlying reasons, desires, or goals that drive a character’s actions and decisions within a narrative.
-
B.
missionOfAntagonist
Indicates the primary goal, plan, or objective that the antagonist is actively pursuing.
-
C.
protagonistAction
Indicates that the referenced entity performs the central or primary action associated with the main character in a narrative or scenario.
-
D.
narrativeGoal
chosen
Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
-
E.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e679108b1481909677cf80e8e77e76 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.