Triple
T29306637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halo Infinite |
E743111
|
entity |
| Predicate | initiallyPlannedReleaseYear |
P14322
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Halo Infinite, initiallyPlannedReleaseYear, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyPlannedReleaseYear Context triple: [Halo Infinite, initiallyPlannedReleaseYear, 2020]
-
A.
originalPlannedLaunchYear
chosen
Indicates the year that was initially scheduled or intended for an entity’s launch before any delays or changes.
-
B.
yearOfLaunch
Indicates the specific calendar year in which an entity (such as a product, mission, or project) was first launched or released.
-
C.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
D.
yearAnnounced
Indicates the calendar year in which something (such as a product, event, or decision) was formally announced.
-
E.
plannedEndYear
Indicates the calendar year in which an activity, project, or plan is intended or scheduled to be completed.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 1:14 p.m.