Triple
T37471026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Cinders |
E931151
|
entity |
| Predicate | obtainmentFrequency |
P171897
|
FINISHED |
| Object | weekly-limited |
—
|
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: weekly-limited | Statement: [Soul Cinders, obtainmentFrequency, weekly-limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obtainmentFrequency Context triple: [Soul Cinders, obtainmentFrequency, weekly-limited]
-
A.
dealFrequency
Indicates how often a particular deal, transaction, or agreement occurs within a given period.
-
B.
contributionFrequency
Indicates how often a contribution or set of contributions occurs within a given period.
-
C.
usualFrequency
chosen
Indicates how often an action, event, or relationship typically occurs within a given time frame.
-
D.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
E.
recommendedUsageFrequency
Indicates how often something is advised or prescribed to be used within a given time period.
- 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_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.