Triple
T6568150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt Schaub |
E153964
|
entity |
| Predicate | careerNFLTouchdownPasses |
P17447
|
FINISHED |
| Object | over 130 |
—
|
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: over 130 | Statement: [Matt Schaub, careerNFLTouchdownPasses, over 130]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: careerNFLTouchdownPasses Context triple: [Matt Schaub, careerNFLTouchdownPasses, over 130]
-
A.
careerNFLTouchdowns
Indicates the total number of touchdowns a player has scored over the course of their NFL career.
-
B.
ledNFLInPassingTouchdowns
Indicates that the subject was the league leader in passing touchdowns in the NFL for a given season or time period.
-
C.
gameWinningTouchdownPasser
Indicates that the subject is the player who threw the touchdown pass that secured the victory in the game for the subject's team.
-
D.
passingTouchdownsCareer
chosen
Indicates the total number of touchdown passes a player has thrown over the course of their entire career.
-
E.
careerTotalTouchdowns
Indicates the total number of touchdowns an entity has scored over the entire duration of its 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:53 p.m.