Triple
T5992986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACC Coach of the Year |
E133396
|
entity |
| Predicate | confersRecognitionOn |
P35290
|
FINISHED |
| Object | head coaches |
—
|
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: head coaches | Statement: [ACC Coach of the Year, confersRecognitionOn, head coaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confersRecognitionOn Context triple: [ACC Coach of the Year, confersRecognitionOn, head coaches]
-
A.
grantsRecognitionTo
chosen
Indicates that one entity formally acknowledges, honors, or validates another entity’s achievements, status, or contributions.
-
B.
granteeRecognition
Indicates that an entity acknowledges, credits, or formally recognizes a grantee for their role, contribution, or status in relation to a grant.
-
C.
notableAwardRecognition
Indicates that an entity has received or been formally recognized with a notable award or honor.
-
D.
fieldOfRecognition
Indicates the domain, discipline, or area in which an entity is formally acknowledged, honored, or recognized.
-
E.
recognizesWorkOf
Indicates that one entity acknowledges, identifies, or gives credit to the work or contributions produced by another entity.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e9189908190abc9c742b38dfabc |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.