Triple
T19597265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pashupatastra |
E470377
|
entity |
| Predicate | consequenceOfMisuse |
P21521
|
FINISHED |
| Object | destruction of the wielder |
—
|
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 wielder | Statement: [Pashupatastra, consequenceOfMisuse, destruction of the wielder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfMisuse Context triple: [Pashupatastra, consequenceOfMisuse, destruction of the wielder]
-
A.
misuseCanConstitute
chosen
Indicates that improper or incorrect use of something can amount to, or be considered as, a particular offense, violation, or condition.
-
B.
consequenceOfApplication
Indicates that something occurs as a result or outcome of a particular application or use of something.
-
C.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
D.
violationConsequences
Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
-
E.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407b997881909762c8f919c9cdad |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.