Triple
T14946561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backyard Brawl |
E372676
|
entity |
| Predicate | hasBreakInSeries |
P56828
|
FINISHED |
| Object | football series hiatus after 2011 season |
—
|
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 hiatus after 2011 season | Statement: [Backyard Brawl, hasBreakInSeries, football series hiatus after 2011 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreakInSeries Context triple: [Backyard Brawl, hasBreakInSeries, football series hiatus after 2011 season]
-
A.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
B.
breaksOn
Indicates that one entity fractures, shatters, or fails when subjected to contact with or force from another entity.
-
C.
breakType
chosen
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
D.
isBrokenBy
Indicates that one entity causes another entity to become damaged, nonfunctional, or destroyed.
-
E.
hasMaximumBreaks
Indicates that there is an upper limit on the number of breaks allowed or assigned in a given context.
- 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.