Triple
T23715920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollow |
E586001
|
entity |
| Predicate | previewReleaseDate |
P153675
|
FINISHED |
| Object | 2012-12-18 |
—
|
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: 2012-12-18 | Statement: [Hollow, previewReleaseDate, 2012-12-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previewReleaseDate Context triple: [Hollow, previewReleaseDate, 2012-12-18]
-
A.
earlyAccessReleaseDate
Indicates the date on which something is first made available to a limited or pre-release audience before its full public release.
-
B.
originallyScheduledReleaseDate
Indicates the date on which something was first planned or intended to be released, before any later changes or rescheduling.
-
C.
betaReleaseDate
Indicates the date on which a product or system is first released in its beta version for testing or limited use.
-
D.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
-
E.
releaseSchedule
Indicates the planned timing and sequence for when something (such as a product, update, or content) will be made available or launched.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b77ab1bc8190be72606d363a07a0 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 6:54 p.m.