Triple
T37538572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2 |
E933270
|
entity |
| Predicate | initialConsoleReleaseDate |
P193393
|
FINISHED |
| Object | 2017-09-06 |
—
|
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-09-06 | Statement: [Destiny 2, initialConsoleReleaseDate, 2017-09-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialConsoleReleaseDate Context triple: [Destiny 2, initialConsoleReleaseDate, 2017-09-06]
-
A.
platformFirstReleased
Indicates the date or time when a platform was initially released or made publicly available.
-
B.
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.
-
C.
virtualConsoleReleaseDateNorthAmerica
Indicates the date on which something was released on the Virtual Console service in North America.
-
D.
firstShortReleaseDate
Indicates the earliest (first) date on which a short version or short-format release of something became publicly available.
-
E.
firstPublicReleaseDevice
Indicates that the subject is the device on which something (e.g., a product, feature, or software) was first publicly released.
- 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_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: May 3, 2026, 4:17 p.m.