Triple
T1167618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AP NFL Coach of the Year |
E24833
|
entity |
| Predicate | recognizesPerformanceIn |
P1597
|
FINISHED |
| Object | regular season |
—
|
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: regular season | Statement: [AP NFL Coach of the Year, recognizesPerformanceIn, regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesPerformanceIn Context triple: [AP NFL Coach of the Year, recognizesPerformanceIn, regular season]
-
A.
fieldOfRecognition
chosen
Indicates the domain, discipline, or area in which an entity is formally acknowledged, honored, or recognized.
-
B.
awardOrRanking
Indicates that there is an award, honor, or ranking status conferred on or associated with an entity.
-
C.
eligiblePerformers
Indicates that certain entities are qualified or permitted to perform in a specified event, role, or context.
-
D.
notableWorkPerformed
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
-
E.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccd75048190b8ce88237c1a748b |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.