Triple
T38061389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve of Destruction |
E950347
|
entity |
| Predicate | isClimacticBattle |
P136284
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eve of Destruction, isClimacticBattle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClimacticBattle Context triple: [Eve of Destruction, isClimacticBattle, true]
-
A.
isClimacticDuelOf
Indicates that one event or confrontation serves as the decisive, peak showdown within the narrative arc of another event or storyline.
-
B.
mainBattle
Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, or entity.
-
C.
epicBattle
Indicates a large-scale, intense conflict or confrontation between opposing entities, often marked by extraordinary stakes or dramatic significance.
-
D.
climacticAct
chosen
Indicates the pivotal or most intense action or event that serves as the climax within a sequence or narrative.
-
E.
hasTacticalBattles
Indicates that there are one or more specific tactical-level combat engagements occurring between the related entities.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.