Triple
T3106587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indianapolis Jets |
E64844
|
entity |
| Predicate | madePlayoffs1948–49 |
P45973
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Indianapolis Jets, madePlayoffs1948–49, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madePlayoffs1948–49 Context triple: [Indianapolis Jets, madePlayoffs1948–49, false]
-
A.
madePlayoffs1946_47
Indicates that a team qualified for and participated in the playoffs during the 1946–1947 season.
-
B.
seasonRecord1946_47
Indicates the performance or record associated with the 1946–47 season for a team, player, or entity.
-
C.
playedInPostseasonFor
Indicates that an athlete participated in postseason games or competitions as a member of a specified team or organization.
-
D.
madePlayoffsFirstTime
Indicates that an entity qualified for the playoffs for the first time in its history or participation.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29d4aa8819093287bc71370fc05 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.