Triple
T32565328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvin Johnson |
E832345
|
entity |
| Predicate | singleSeasonReceivingYardsRecordYear |
P175007
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Calvin Johnson, singleSeasonReceivingYardsRecordYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleSeasonReceivingYardsRecordYear Context triple: [Calvin Johnson, singleSeasonReceivingYardsRecordYear, 2012]
-
A.
singleSeasonReceivingYardsRecordHolder
Indicates the entity that holds the record for the most receiving yards accumulated in a single season.
-
B.
singleSeasonReceivingYards
Indicates the total number of receiving yards a player gains during a single season.
-
C.
singleSeasonReceivingYardsSeason
Indicates the total number of receiving yards a player gained in a single football season.
-
D.
singleSeasonRushingYardsRecord
Indicates the record-setting total number of rushing yards accumulated by a player in a single season.
-
E.
thousandYardReceivingSeasons
Indicates that an entity (typically a player) has achieved one or more seasons with at least 1,000 receiving yards.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:03 a.m.