Triple
T707985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Namath |
E14142
|
entity |
| Predicate | AFLDraftStatus |
P14520
|
FINISHED |
| Object | first overall pick |
—
|
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: first overall pick | Statement: [Joe Namath, AFLDraftStatus, first overall pick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AFLDraftStatus Context triple: [Joe Namath, AFLDraftStatus, first overall pick]
-
A.
NFLDraftYear
Indicates the year in which a person was selected in the NFL Draft.
-
B.
draftedIn
Indicates that one entity was selected or recruited into another entity (such as a team, organization, or military service) through a formal draft process.
-
C.
draftedAt
chosen
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
-
D.
draftingPeriod
Indicates the time span during which a document, plan, or agreement is being written, revised, or prepared before it is finalized.
-
E.
draftedUnder
Indicates that one entity was formally selected or conscripted into a role, position, or service according to the authority, rules, or jurisdiction of 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5c011948190b2cfccd8fe722742 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f0217081908268b3f47e72f8df |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.