Triple
T27703927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadowhunter Institute |
E698496
|
entity |
| Predicate | targetEnemies |
P4675
|
FINISHED |
| Object | demons |
—
|
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: demons | Statement: [Shadowhunter Institute, targetEnemies, demons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetEnemies Context triple: [Shadowhunter Institute, targetEnemies, demons]
-
A.
targetsAsRacialEnemy
Indicates that one party identifies and treats another party as an enemy specifically on the basis of their race.
-
B.
battleTarget
Indicates that one entity is the chosen opponent or objective that another entity is engaging or intends to engage in battle.
-
C.
primaryEnemy
chosen
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
D.
enemyTechnologyTargeted
Indicates that a technology belonging to an enemy is being specifically selected or targeted for attack, disruption, or counteraction.
-
E.
primaryEnemyForces
Indicates that the related entities constitute the main opposing or hostile forces in a conflict or competitive situation.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 2:58 p.m.