Triple
T23420224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1979 Houston Oilers season |
E560629
|
entity |
| Predicate | madePlayoffsAs |
P144153
|
FINISHED |
| Object | AFC Wild Card team |
—
|
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: AFC Wild Card team | Statement: [1979 Houston Oilers season, madePlayoffsAs, AFC Wild Card team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madePlayoffsAs Context triple: [1979 Houston Oilers season, madePlayoffsAs, AFC Wild Card team]
-
A.
reachedPlayoffs
chosen
Indicates that a team or competitor successfully qualified for and participated in the playoff stage of a competition.
-
B.
wonPlayoffs
Indicates that a team or player emerged as the overall victor in a playoff series or postseason competition.
-
C.
usesPlayoffs
Indicates that a competition or league determines its final standings or champion through a postseason playoff format rather than solely by regular-season results.
-
D.
madePlayoffsInSeason
Indicates that a team qualified for and participated in the playoffs during a specified season.
-
E.
playedInPostseasonFor
Indicates that an athlete participated in postseason games or competitions as a member of a specified team or organization.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54605dc81909aad9834ef6ff8a1 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:44 p.m.