Triple
T28556856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion of Boom defense era |
E723029
|
entity |
| Predicate | playoffSuccess |
P22048
|
FINISHED |
| Object | multiple deep playoff runs |
—
|
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: multiple deep playoff runs | Statement: [Legion of Boom defense era, playoffSuccess, multiple deep playoff runs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffSuccess Context triple: [Legion of Boom defense era, playoffSuccess, multiple deep playoff runs]
-
A.
playoffAchievement
chosen
Indicates that an entity has reached or accomplished a specific milestone or result in a playoff competition or postseason series.
-
B.
playoffRoundReached
Indicates the specific stage or round of a playoff series that an entity has advanced to or reached.
-
C.
playoffResult
Indicates the outcome of a playoff contest or series between competitors, such as who advanced or was eliminated.
-
D.
wonPlayoffs
Indicates that a team or player emerged as the overall victor in a playoff series or postseason competition.
-
E.
playoffChampionAdvancesTo
Indicates that the team winning a playoff championship progresses to the next specified stage, round, or competition.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6505097348190b46266efd9cd007d |
completed | May 2, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:46 a.m.