Triple
T27879277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slammiversary |
E705042
|
entity |
| Predicate | hasRecurringFrequency |
P7407
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [Slammiversary, hasRecurringFrequency, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecurringFrequency Context triple: [Slammiversary, hasRecurringFrequency, annual]
-
A.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
B.
hasRecurringElement
Indicates that an entity includes an element that appears repeatedly or occurs multiple times within it.
-
C.
tienePeriodicidad
chosen
Indicates that something occurs, recurs, or is scheduled with a specific regular frequency or periodic pattern.
-
D.
hasRepetitionRate
Indicates how frequently an event, action, or pattern recurs within a given context or time frame.
-
E.
hasRecurringRole
Indicates that an entity repeatedly appears or participates in a role within an ongoing or multiple related contexts over time.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: April 27, 2026, 6:29 p.m.