Triple
T29306638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halo Infinite |
E743111
|
entity |
| Predicate | delayedToYear |
P18028
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Halo Infinite, delayedToYear, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delayedToYear Context triple: [Halo Infinite, delayedToYear, 2021]
-
A.
postponedToYear
chosen
Indicates that an event or action has been delayed and rescheduled to occur in the specified calendar year.
-
B.
delayedFrom
Indicates that something is postponed or starts later than originally scheduled due to a cause or source associated with the referenced entity.
-
C.
movedToCurrentDateYear
Indicates that an entity has been moved, updated, or adjusted so that its associated date now falls within the current calendar year.
-
D.
delayedUntil
Indicates that the occurrence or effect of one event or condition is postponed and does not take place until a specified later event, time, or condition is reached.
-
E.
deprecatedYear
Indicates the year in which something (such as a feature, standard, or item) was officially marked as deprecated or no longer recommended for 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a6fbb88190bae8ba90855eadda |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:14 p.m.