Triple
T34797757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonians |
E1003134
|
entity |
| Predicate | racialPowerEffect |
P99991
|
FINISHED |
| Object | rapid health regeneration for a short time |
—
|
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: rapid health regeneration for a short time | Statement: [Argonians, racialPowerEffect, rapid health regeneration for a short time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racialPowerEffect Context triple: [Argonians, racialPowerEffect, rapid health regeneration for a short time]
-
A.
occupationPower
Indicates a relationship where one party holds authoritative control, influence, or dominance over another within the context of an occupation or role.
-
B.
heroPowerEffect
chosen
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
C.
effectOnRace
Indicates that one entity has an influence or impact on the outcome, dynamics, or characteristics of a race.
-
D.
powerCharacter
Indicates that one entity possesses, controls, or exerts power or influence over another entity.
-
E.
invokesPower
Indicates that one entity calls upon, activates, or makes use of the power, authority, or special ability associated with 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.