Triple
T6145322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Fever |
E137059
|
entity |
| Predicate | draftedNumberOneOverallYear |
P69434
|
FINISHED |
| Object | 2024 |
—
|
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: 2024 | Statement: [Indiana Fever, draftedNumberOneOverallYear, 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftedNumberOneOverallYear Context triple: [Indiana Fever, draftedNumberOneOverallYear, 2024]
-
A.
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.
-
B.
overallDraftPickNumber
Indicates the specific overall position at which an entity (such as a player) is selected in a draft relative to all other selections.
-
C.
NFLDraftYear
Indicates the year in which a person was selected in the NFL Draft.
-
D.
ABA draftYear
Indicates the year in which an entity was selected or entered into the ABA draft.
-
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. 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cdd2dc0819080a4adf0cead3603 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:16 p.m.