Triple
T30632787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annatar |
E779755
|
entity |
| Predicate | deceptionTarget |
P150473
|
FINISHED |
| Object | Elves of Eregion |
—
|
NE NERFINISHED |
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: Elves of Eregion | Statement: [Annatar, deceptionTarget, Elves of Eregion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deceptionTarget Context triple: [Annatar, deceptionTarget, Elves of Eregion]
-
A.
typeOfDeception
Indicates the specific kind or category of deceptive act that one entity employs toward another or in a given context.
-
B.
deceptionMotif
Indicates a relationship where one entity employs or embodies a theme of deceit, trickery, or misleading appearance in relation to another entity or situation.
-
C.
deceptionRole
chosen
Indicates a role that an entity plays in an act of deception, such as deceiver, accomplice, or target.
-
D.
usedMeansOfDeception
Indicates that one entity employed a particular method or tool specifically to deceive another entity.
-
E.
threatensDeceptionOf
Indicates that one entity poses or communicates a risk of deceiving or misleading another entity.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a1ee6348190a316b92bccd14826 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:28 p.m.