Triple
T36841764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Miracle |
E910426
|
entity |
| Predicate | secondLateralRecipient |
P200234
|
FINISHED |
| Object | Kenyan Drake |
—
|
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: Kenyan Drake | Statement: [Miami Miracle, secondLateralRecipient, Kenyan Drake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondLateralRecipient Context triple: [Miami Miracle, secondLateralRecipient, Kenyan Drake]
-
A.
secondParty
Indicates that an entity participates in a relationship or transaction as the second party relative to a primary (first) party.
-
B.
secondHolder
Indicates that an entity is the second person or party to hold or possess a particular item, role, title, or position in a sequence.
-
C.
secondedBy
Indicates that an initial proposal, motion, or action by one entity is formally supported or endorsed by another entity as a second.
-
D.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
E.
side2
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69ff7bbfa4b08190b11e84861706b349 |
completed | May 9, 2026, 6:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.