Triple
T36841762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Miracle |
E910426
|
entity |
| Predicate | receiverOfInitialPass |
P78657
|
FINISHED |
| Object | Kenny Stills |
—
|
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: Kenny Stills | Statement: [Miami Miracle, receiverOfInitialPass, Kenny Stills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receiverOfInitialPass Context triple: [Miami Miracle, receiverOfInitialPass, Kenny Stills]
-
A.
initialReception
Indicates the nature or quality of the first response or reaction something receives when it is introduced or presented.
-
B.
recipientOf
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
C.
intendedReceiver
Indicates that one entity is the target or designated recipient of something (such as a message, item, or action) originating from another entity.
-
D.
Receiver
chosen
Indicates the entity that is the target or beneficiary of an action, transfer, or communication initiated by another entity.
-
E.
firstRecipientTeam
Indicates the team that initially receives something (such as an item, message, or responsibility) before any others.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:13 p.m.