Triple
T11116668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984–85 NFL playoffs |
E262901
|
entity |
| Predicate | wildCardRoundIncluded |
P15100
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1984–85 NFL playoffs, wildCardRoundIncluded, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wildCardRoundIncluded Context triple: [1984–85 NFL playoffs, wildCardRoundIncluded, true]
-
A.
hasRound
chosen
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
B.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
C.
includesSecondRound
Indicates that the referenced process, event, or activity contains or involves a second round or phase as part of its structure.
-
D.
winnerPlaysIn
Indicates that the entity identified as the winner of a contest or match participates in a subsequent game, round, or event.
-
E.
hasQualifyingRounds
Indicates that an event or competition includes preliminary qualifying rounds that participants must complete before advancing further.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa81d8c81908a387b56cbcc9128 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.