Triple
T16889832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 NHL All-Star Game |
E421636
|
entity |
| Predicate | fantasyDraftDate |
P124869
|
FINISHED |
| Object | 2011-01-28 |
—
|
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: 2011-01-28 | Statement: [2011 NHL All-Star Game, fantasyDraftDate, 2011-01-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fantasyDraftDate Context triple: [2011 NHL All-Star Game, fantasyDraftDate, 2011-01-28]
-
A.
draftingPeriod
Indicates the time span during which a document, plan, or agreement is being written, revised, or prepared before it is finalized.
-
B.
draftedAt
Indicates that an entity was selected or chosen by another entity at a specific draft event or position.
-
C.
draftedAfter
Indicates that one entity was selected or formally drafted at a later time than another entity.
-
D.
draftedDuring
Indicates that an entity was formally selected or conscripted (e.g., into military service or a professional league) within the time span of a specified event or period.
-
E.
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.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc3b5188190ac713b4d4166e961 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32e2c07b081908c8fee9f5507bb9e |
completed | April 18, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:29 a.m.