Triple
T14946562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backyard Brawl |
E372676
|
entity |
| Predicate | seriesResumed |
P44197
|
FINISHED |
| Object | football series renewed in 2022 |
—
|
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: football series renewed in 2022 | Statement: [Backyard Brawl, seriesResumed, football series renewed in 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesResumed Context triple: [Backyard Brawl, seriesResumed, football series renewed in 2022]
-
A.
resumedIn
chosen
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
B.
seriesRun
Indicates that one entity is a specific run, edition, or installment within an ongoing series associated with another entity.
-
C.
seriesStatus
Indicates the current state or phase of a series within its lifecycle (e.g., ongoing, completed, canceled, or planned).
-
D.
seriesRunStart
Indicates the point in time or event at which a particular series or sequence of related items begins.
-
E.
seriesEndStatus
Indicates the final outcome or completion state of a series within a larger sequence or collection.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68e35c481908e47cd68441c5115 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:39 a.m.