Triple
T17422366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2012 NHL All-Star Game |
E423646
|
entity |
| Predicate | fantasyDraftFormatUsed |
P127396
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [2012 NHL All-Star Game, fantasyDraftFormatUsed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fantasyDraftFormatUsed Context triple: [2012 NHL All-Star Game, fantasyDraftFormatUsed, yes]
-
A.
fantasyDraftDate
Indicates the date on which a fantasy draft event is scheduled or took place.
-
B.
usedInFantasySportsPlatforms
Indicates that something (such as data, content, or a feature) is utilized within fantasy sports platforms for gameplay, management, or related functionality.
-
C.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
D.
ドラフト種別
Indicates the type or category of a draft in relation to how it was created, selected, or classified.
-
E.
draftingPeriod
Indicates the time span during which a document, plan, or agreement is being written, revised, or prepared before it is finalized.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44237f2cc819083ca0e7e00d828fb |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.