Triple
T9690487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horizon Zero Dawn |
E234522
|
entity |
| Predicate | salesMilestoneDate |
P12595
|
FINISHED |
| Object | 2022-02 |
—
|
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: 2022-02 | Statement: [Horizon Zero Dawn, salesMilestoneDate, 2022-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salesMilestoneDate Context triple: [Horizon Zero Dawn, salesMilestoneDate, 2022-02]
-
A.
salesMilestone
chosen
Indicates that a specific sales target or threshold has been reached or surpassed.
-
B.
marketingMilestone
Indicates a significant event or achievement within a marketing effort that marks progress toward marketing goals or phases.
-
C.
revenueDate
Indicates the date on which revenue is recognized, recorded, or attributed in relation to a transaction or financial event.
-
D.
digitalSalesMilestone
Indicates that a specific target or significant achievement has been reached in the context of digital product or service sales.
-
E.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
- 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.