Triple
T13487505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destroyer of Enemies |
E318543
|
entity |
| Predicate | impliesAction |
P51427
|
FINISHED |
| Object | vanquishing enemies |
—
|
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: vanquishing enemies | Statement: [Destroyer of Enemies, impliesAction, vanquishing enemies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesAction Context triple: [Destroyer of Enemies, impliesAction, vanquishing enemies]
-
A.
implies
Indicates that the truth of one statement guarantees or leads logically to the truth of another statement.
-
B.
impliesRole
Indicates that one role logically entails or gives rise to another role within a given context or system.
-
C.
implementsAct
Indicates that one entity carries out, executes, or puts into effect a specified act, plan, or directive associated with another entity.
-
D.
impliesStatus
Indicates that one condition, fact, or state logically leads to or determines another status or outcome.
-
E.
refersToAction
chosen
Indicates that one entity explicitly points to, mentions, or designates a specific action or event.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3b9b488190bb4e11424ff599c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.