Triple
T9690489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horizon Zero Dawn |
E234522
|
entity |
| Predicate | dlcReleaseDate |
P50108
|
FINISHED |
| Object | 2017-11-07 |
—
|
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-11-07 | Statement: [Horizon Zero Dawn, dlcReleaseDate, 2017-11-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dlcReleaseDate Context triple: [Horizon Zero Dawn, dlcReleaseDate, 2017-11-07]
-
A.
hasDLC
Indicates that one entity includes, is associated with, or is supplemented by another entity as downloadable content.
-
B.
expansionReleaseDate
chosen
Indicates the date on which an expansion (such as an add-on or supplementary release) is officially made available.
-
C.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
D.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
E.
betaReleaseDate
Indicates the date on which a product or system is first released in its beta version for testing or limited use.
- F. None of above.
Provenance (3 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d0422e88190a234ba74eb0dad25 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.