Triple
T38076254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1969 NFL season |
E950718
|
entity |
| Predicate | SuperBowlFollowingSeason |
P10041
|
FINISHED |
| Object | Super Bowl IV |
—
|
NE NERFINISHED |
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: Super Bowl IV | Statement: [1969 NFL season, SuperBowlFollowingSeason, Super Bowl IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SuperBowlFollowingSeason Context triple: [1969 NFL season, SuperBowlFollowingSeason, Super Bowl IV]
-
A.
SuperBowlSeason
Indicates that a particular season is identified as the one in which a given Super Bowl game is played or associated.
-
B.
superBowlSeason
Indicates that a particular NFL season is the one in which a specified Super Bowl game took place.
-
C.
ProBowlSeason
Indicates that a player was selected to participate in the Pro Bowl during a specific season.
-
D.
nextSuperBowl
chosen
Indicates that one event is the immediately upcoming occurrence of the Super Bowl relative to a given reference point or time.
-
E.
SuperBowl
Indicates that the entities are related through the NFL championship game known as the Super Bowl, such as being its participants, location, winner, or associated event.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:21 p.m.