Triple
T14074827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beast Quake run vs New Orleans Saints |
E338703
|
entity |
| Predicate | yardageAfterContact |
P34478
|
FINISHED |
| Object | majority of 67 yards after contact |
—
|
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: majority of 67 yards after contact | Statement: [Beast Quake run vs New Orleans Saints, yardageAfterContact, majority of 67 yards after contact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yardageAfterContact Context triple: [Beast Quake run vs New Orleans Saints, yardageAfterContact, majority of 67 yards after contact]
-
A.
yardsPerReception
Indicates the average number of yards gained each time a player makes a reception.
-
B.
hasYard
Indicates that one entity possesses or includes a yard as part of its property or premises.
-
C.
interceptionYardLine
Indicates the yard line on the field where an interception occurs during a play.
-
D.
hasYardage
chosen
Indicates that something possesses or is associated with a specific measured distance or length, typically expressed in yards.
-
E.
yardsFromScrimmageCareerNFL
Indicates the total number of yards a player has gained from scrimmage over their entire NFL career.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5bc49881909012b66fa451f495 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.