Triple
T8521759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwight Freeney |
E201707
|
entity |
| Predicate | forcedFumblesNFL |
P41413
|
FINISHED |
| Object | 47 |
—
|
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: 47 | Statement: [Dwight Freeney, forcedFumblesNFL, 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedFumblesNFL Context triple: [Dwight Freeney, forcedFumblesNFL, 47]
-
A.
careerForcedFumbles
chosen
Indicates the total number of times a player has caused an opponent to lose possession of the ball via a fumble over the course of their entire career.
-
B.
decidingPlayFumbleForcedBy
Indicates that a deciding play in a game is characterized by a fumble that was forced by a particular entity (e.g., player or team).
-
C.
fumbleReturnTouchdowns
Indicates the number of touchdowns a player or team scores by recovering an opponent’s fumble and returning it to the end zone.
-
D.
decidingPlayFumbleRecoveredBy
Indicates that a particular play is determined or ruled based on which player or team recovered a fumbled ball.
-
E.
careerFumbleRecoveries
Indicates the total number of times an entity has recovered a fumble over the course of their entire 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe62a490481908ee0ad4ba9a94682 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.