Triple
T23743457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zacch Pickens |
E586748
|
entity |
| Predicate | isDraftedPlayerIn |
P1035
|
FINISHED |
| Object | NFL Draft |
—
|
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: NFL Draft | Statement: [Zacch Pickens, isDraftedPlayerIn, NFL Draft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDraftedPlayerIn Context triple: [Zacch Pickens, isDraftedPlayerIn, NFL Draft]
-
A.
hasDraftedPlayersTo
Indicates that one entity has selected or drafted players to join or belong to another entity, such as a team, league, or organization.
-
B.
draftedFor
Indicates that one entity has been selected or assigned, typically through a draft process, to serve, play, or work for another entity.
-
C.
draftedInPeriod
Indicates that an entity was formally drafted or selected during a specified time period.
-
D.
wasAlsoDraftedBy
Indicates that an entity was additionally selected or drafted by another party, beyond any primary or initial drafting entity.
-
E.
draftedIn
chosen
Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcbbcf988190b56d74af4b126bd8 |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:12 p.m.