Triple
T37538573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2 |
E933270
|
entity |
| Predicate | initialWindowsReleaseDate |
P193445
|
FINISHED |
| Object | 2017-10-24 |
—
|
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: 2017-10-24 | Statement: [Destiny 2, initialWindowsReleaseDate, 2017-10-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialWindowsReleaseDate Context triple: [Destiny 2, initialWindowsReleaseDate, 2017-10-24]
-
A.
initialConsoleReleaseDate
Indicates the calendar date on which a console was first released to the public.
-
B.
windowsReleaseYear
Indicates the calendar year in which a specific version or edition of Microsoft Windows was officially released.
-
C.
windowsReleaseDate
Indicates the calendar date on which a specific version of Microsoft Windows was officially released.
-
D.
initialReleaseApprox
Indicates that an entity’s first release or debut occurred around an estimated or approximate point in time rather than on a precisely known date.
-
E.
firstShortReleaseDate
Indicates the earliest (first) date on which a short version or short-format release of something became publicly available.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: May 3, 2026, 4:17 p.m.