Triple
T37471153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coldheart Interstitia |
E931154
|
entity |
| Predicate | rewardSourceFor |
P35526
|
FINISHED |
| Object | Soul Ash |
—
|
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: Soul Ash | Statement: [Coldheart Interstitia, rewardSourceFor, Soul Ash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardSourceFor Context triple: [Coldheart Interstitia, rewardSourceFor, Soul Ash]
-
A.
rewardFulfilledFor
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
-
B.
claimsSource
Indicates that one entity is identified as the origin or provider of a claim made by another entity.
-
C.
rewardRecipient
Indicates the entity that receives a reward as a result of some action, event, or decision.
-
D.
rewardScope
Indicates the extent, range, or conditions under which a reward applies within a given context or system.
-
E.
rewardUse
chosen
Indicates that one entity grants or provides a reward in response to the use or utilization of 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:17 p.m.