Triple
T38592230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skill Rating |
E932479
|
entity |
| Predicate | resetsFrequency |
P121255
|
FINISHED |
| Object | at the start of each competitive season (soft reset) |
—
|
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: at the start of each competitive season (soft reset) | Statement: [Skill Rating, resetsFrequency, at the start of each competitive season (soft reset)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resetsFrequency Context triple: [Skill Rating, resetsFrequency, at the start of each competitive season (soft reset)]
-
A.
replacedFrequency
Indicates how often one entity is substituted for or takes the place of another over a given period.
-
B.
measurementFrequency
Indicates how often a measurement is taken or recorded over time.
-
C.
memoryResets
chosen
Indicates that an entity’s memory is cleared, reverted, or restarted, removing or resetting previously stored information.
-
D.
replayFrequency
Indicates how often an event, action, or sequence is repeated or played back over a given period.
-
E.
serviceFrequencyType
Indicates how often a service occurs or is scheduled 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.