Triple
T37664447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Guardian |
E937789
|
entity |
| Predicate | statusEffectTrigger |
P196067
|
FINISHED |
| Object | Periodically applied to nearby players |
—
|
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: Periodically applied to nearby players | Statement: [Elder Guardian, statusEffectTrigger, Periodically applied to nearby players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusEffectTrigger Context triple: [Elder Guardian, statusEffectTrigger, Periodically applied to nearby players]
-
A.
effectTrigger
chosen
Indicates that one event, condition, or action initiates or causes another effect to occur.
-
B.
instantEffect
Indicates that one event or action produces its effect immediately at the same moment it occurs, without any delay.
-
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.
conditionalEffect
Indicates that one event, state, or action occurs or holds only if a specified condition is met.
-
E.
magicTrigger
Indicates that one entity initiates or activates a magical effect, condition, or event upon another entity or context.
- 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_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:18 p.m.