Triple
T2550030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krikkit war |
E56601
|
entity |
| Predicate | goalOfBelligerent |
P38945
|
FINISHED |
| Object | destruction of the universe |
—
|
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: destruction of the universe | Statement: [Krikkit war, goalOfBelligerent, destruction of the universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfBelligerent Context triple: [Krikkit war, goalOfBelligerent, destruction of the universe]
-
A.
conflictBelligerent
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
-
B.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
-
C.
belligerentInterest
Indicates that an entity has a hostile, aggressive, or conflict-seeking attitude or stake toward another entity or situation.
-
D.
aimOfAttacker
chosen
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
-
E.
objectiveOfAttackers
Indicates the target or goal that attackers aim to reach or affect through their attack.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.