Triple
T37508300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drust invasion of Ardenweald |
E932152
|
entity |
| Predicate | goalOfAntagonists |
P108466
|
FINISHED |
| Object | corrupt Ardenweald |
—
|
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: corrupt Ardenweald | Statement: [Drust invasion of Ardenweald, goalOfAntagonists, corrupt Ardenweald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfAntagonists Context triple: [Drust invasion of Ardenweald, goalOfAntagonists, corrupt Ardenweald]
-
A.
missionOfAntagonist
chosen
Indicates the primary goal, plan, or objective that the antagonist is actively pursuing.
-
B.
primaryAntagonists
Indicates that the referenced entities serve as the main opposing or adversarial forces in relation to a specified subject or narrative.
-
C.
primaryAntagonistType
Indicates the role or category of the main opposing force or adversary that serves as the central source of conflict.
-
D.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
E.
antagonistActionOf
Indicates that one entity performs an action in opposition or hostility toward another entity, acting as its antagonist.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.