Triple
T28902189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple S1 |
E732976
|
entity |
| Predicate | announcementEventType |
P2787
|
FINISHED |
| Object | Apple product launch event |
—
|
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: Apple product launch event | Statement: [Apple S1, announcementEventType, Apple product launch event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcementEventType Context triple: [Apple S1, announcementEventType, Apple product launch event]
-
A.
announcementOccasion
chosen
Indicates the specific event, context, or circumstance on the basis of which an announcement is made.
-
B.
announcementFormula
Indicates that one entity is the formal content or wording used in an announcement made by another entity.
-
C.
notificationType
Indicates the specific category or kind of notification associated with an event or action.
-
D.
publishedEvent
Indicates that an entity has formally released or made an event publicly available or announced.
-
E.
announcementMadeBy
Indicates that a particular announcement is issued or created by a specific entity (such as a person, organization, or system).
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa8deec8190b1eef143e10c9598 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:04 a.m.