Triple
T35833030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mel Blount rule |
E1035850
|
entity |
| Predicate | distanceLimitFromLineOfScrimmage |
P206071
|
FINISHED |
| Object | 5 yards |
—
|
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: 5 yards | Statement: [Mel Blount rule, distanceLimitFromLineOfScrimmage, 5 yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceLimitFromLineOfScrimmage Context triple: [Mel Blount rule, distanceLimitFromLineOfScrimmage, 5 yards]
-
A.
lineOfScrimmage
Indicates the position on the field where the ball is placed and play begins, separating the offensive and defensive sides before the snap.
-
B.
ledLeagueInYardsFromScrimmage
Indicates that the subject achieved the highest total yards gained from scrimmage in the league for a given season or period.
-
C.
yardsShortOfEndZone
Indicates the number of yards separating a team or ball’s current field position from the opponent’s end zone.
-
D.
interceptionYardLine
Indicates the yard line on the field where an interception occurs during a play.
-
E.
outfieldWallDistance
Indicates the measured distance from home plate to the outfield wall at a particular point or area on the field.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.