Triple
T34059293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for the Barrel |
E873445
|
entity |
| Predicate | renewedAnnuallySince |
P149409
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Battle for the Barrel, renewedAnnuallySince, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renewedAnnuallySince Context triple: [Battle for the Barrel, renewedAnnuallySince, 1994]
-
A.
activatedAnnuallyUntil
Indicates that an action or state is activated once each year and continues to do so repeatedly up to, but not beyond, a specified end date.
-
B.
laterRenewedFor
Indicates that an existing agreement, contract, or arrangement was renewed again at a subsequent, later time.
-
C.
laterRenewedAs
Indicates that an entity was subsequently renewed, reissued, or continued under a later, distinct entity or version.
-
D.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
-
E.
reaffirmationYear
chosen
Indicates the year in which a previously established agreement, decision, or commitment is formally confirmed or renewed.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70b97e92c8190886fdc3808c18650 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.