Triple
T9027617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vision |
E216086
|
entity |
| Predicate | announcedOnDate |
P429
|
FINISHED |
| Object | 2023-06-05 |
—
|
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: 2023-06-05 | Statement: [Vision, announcedOnDate, 2023-06-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedOnDate Context triple: [Vision, announcedOnDate, 2023-06-05]
-
A.
announcedAt
Indicates that an announcement or declaration was made at a specific time or event.
-
B.
announcementDate
chosen
Indicates the date on which an announcement is formally made or becomes publicly known.
-
C.
announcedAfter
Indicates that one announcement occurred later in time than another specified announcement.
-
D.
announcedWith
Indicates that one entity was publicly revealed, declared, or introduced at the same time as, and in explicit association with, another entity.
-
E.
announcedAvailability
Indicates that an entity has publicly communicated that something will be obtainable or accessible, typically starting at a specified time or under certain conditions.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7fcb308190af90d6be8700e498 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.