Triple
T5510572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Harrison |
E144551
|
entity |
| Predicate | undraftedFreeAgentSigningYear |
P10042
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [James Harrison, undraftedFreeAgentSigningYear, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undraftedFreeAgentSigningYear Context triple: [James Harrison, undraftedFreeAgentSigningYear, 2002]
-
A.
undraftedYear
chosen
Indicates the year in which an individual was eligible for a draft but was not selected by any team.
-
B.
signedAsUndraftedFreeAgentBy
Indicates that a player joined a team by signing a contract as an undrafted free agent, rather than being selected in a draft.
-
C.
undrafted
Indicates that an entity, typically a player or candidate, was not selected during a formal drafting or selection process.
-
D.
yearDrafted
Indicates the specific year in which an entity (typically a person, such as an athlete or player) was selected or chosen in a formal draft process.
-
E.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f4cbc2c819091fcbff5f39ceeb4 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.