Triple
T37664129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illager |
E937782
|
entity |
| Predicate | statusEffectSource |
P100843
|
FINISHED |
| Object | Bad Omen (via killing raid captain) |
—
|
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: Bad Omen (via killing raid captain) | Statement: [Illager, statusEffectSource, Bad Omen (via killing raid captain)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusEffectSource Context triple: [Illager, statusEffectSource, Bad Omen (via killing raid captain)]
-
A.
effectSource
Indicates that one entity is the origin or cause from which a particular effect, outcome, or influence arises for another entity.
-
B.
hasStatusEffectSource
chosen
Indicates that a status effect currently applied to an entity originates from, or was caused by, a specific source entity or event.
-
C.
specialEffect
Indicates that one entity produces, applies, or is associated with a distinctive, often non-standard effect on another entity or on an event.
-
D.
grantsStatusEffect
Indicates that one entity applies or bestows a specific status effect onto another entity.
-
E.
effectCount
Indicates the number of distinct effects or outcomes associated with a given action, event, or 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
Created at: May 3, 2026, 4:18 p.m.