Triple
T20793289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Age series |
E511832
|
entity |
| Predicate | featuresAntagonisticForce |
P108467
|
FINISHED |
| Object | darkspawn |
—
|
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: darkspawn | Statement: [Dragon Age series, featuresAntagonisticForce, darkspawn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAntagonisticForce Context triple: [Dragon Age series, featuresAntagonisticForce, darkspawn]
-
A.
featuresAntagonistEntity
chosen
Indicates that the subject includes or involves an entity serving as an antagonist in the context of a narrative, interaction, or scenario.
-
B.
opponentForceCharacteristic
Indicates a characteristic or attribute that describes the nature, capability, or condition of an opposing force.
-
C.
antagonistAttribute
Indicates that an entity possesses a characteristic or role specifically associated with being an antagonist in a narrative or 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2aadd7081908c6343821e8c655c |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.