Triple
T8820640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWDC 2023 |
E209893
|
entity |
| Predicate | announcedAPI |
P84806
|
FINISHED |
| Object | updated SwiftUI APIs |
—
|
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: updated SwiftUI APIs | Statement: [WWDC 2023, announcedAPI, updated SwiftUI APIs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedAPI Context triple: [WWDC 2023, announcedAPI, updated SwiftUI APIs]
-
A.
announcedWith
Indicates that one entity was publicly revealed, declared, or introduced at the same time as, and in explicit association with, another entity.
-
B.
announcedPlatform
Indicates that an entity has publicly revealed or introduced a particular platform (such as a system, service, or technology).
-
C.
announcedTest
Indicates that an entity has formally communicated or made public the existence or details of a test.
-
D.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, another entity.
-
E.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
- F. None of above. chosen
Provenance (4 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600fbbac8190ad36d93fff60a33f |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:46 p.m.