Triple
T24744393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 NFL season |
E618653
|
entity |
| Predicate | MVPOfFinalGame |
P157079
|
FINISHED |
| Object | Joe Montana |
—
|
NE NERFINISHED |
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: Joe Montana | Statement: [1981 NFL season, MVPOfFinalGame, Joe Montana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPOfFinalGame Context triple: [1981 NFL season, MVPOfFinalGame, Joe Montana]
-
A.
MVP
Indicates that an entity has been selected or recognized as the “Most Valuable Player,” i.e., the most outstanding or impactful participant within a specific game, season, event, or context.
-
B.
MVPType
Indicates the specific category or role of a person or entity designated as the “Most Valuable Player” (MVP) within a given context or system.
-
C.
MVPOfSeries
Indicates that an entity was selected as the Most Valuable Player (MVP) for a particular series.
-
D.
MVPOfALCS
Indicates that an entity was selected as the Most Valuable Player of a particular American League Championship Series.
-
E.
MVPposition
Indicates the position or role in which an entity served when it was recognized as the Most Valuable Player (MVP).
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:20 a.m.