Triple
T36841900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Gase |
E910429
|
entity |
| Predicate | notableEventCoached |
P136728
|
FINISHED |
| Object | Miracle in Miami |
E2201181
|
NE 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: Miracle in Miami | Statement: [Adam Gase, notableEventCoached, Miracle in Miami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventCoached Context triple: [Adam Gase, notableEventCoached, Miracle in Miami]
-
A.
notableCoach
Indicates that one entity is a coach who is widely recognized or distinguished in relation to the other entity.
-
B.
notableGameCoached
chosen
Indicates that a person served as a coach in a particular notable game or match.
-
C.
hasCoachedFor
Indicates that one entity has served in a coaching role for another entity, such as a team, organization, or individual.
-
D.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
E.
notableCoachesInvolved
Indicates that certain coaches, recognized for their significance or prominence, were involved in relation to the subject entity.
- F. None of above.
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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dfad8105c8190acdd94fed2db7e89 |
completed | June 26, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.