Triple
T30302185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1977 NFL Draft |
E770680
|
entity |
| Predicate | roundsReductionEffectiveSeason |
P169389
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [1977 NFL Draft, roundsReductionEffectiveSeason, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundsReductionEffectiveSeason Context triple: [1977 NFL Draft, roundsReductionEffectiveSeason, 1977]
-
A.
seasonRound
Indicates that an event, competition, or activity occurs within a specific round or phase of a season-long sequence.
-
B.
roundsReducedSecurity
Indicates that the number of rounds in a process or protocol has been decreased in a way that lowers its security level.
-
C.
hasSeasonalRound
Indicates a recurring, seasonally patterned cycle of movements, activities, or resource use associated with an entity over the course of a year.
-
D.
numberOfRoundRobinGamesPerTeam
Indicates the number of games each team plays in a round-robin competition format.
-
E.
relegationRound
Indicates that entities are involved in a stage or match of a competition where participants risk being demoted to a lower division or tier.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813b03c881909786514932f103f3 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:49 p.m.