Triple
T5100816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple WWDC 2017 |
E114975
|
entity |
| Predicate | announcedProgram |
P61107
|
FINISHED |
| Object | Swift Playgrounds updates |
—
|
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: Swift Playgrounds updates | Statement: [Apple WWDC 2017, announcedProgram, Swift Playgrounds updates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedProgram Context triple: [Apple WWDC 2017, announcedProgram, Swift Playgrounds updates]
-
A.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
B.
broadcastProgram
Indicates that a media outlet or channel transmits a specific program to an audience via a broadcast medium.
-
C.
announcedAs
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by another entity.
-
D.
agencyProgramme
Indicates that an agency is responsible for, manages, or is associated with a particular programme.
-
E.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd758381dc8190ac491788d27ab8e0 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd738ac2e0819099c06cdcc5e21d28 |
completed | March 20, 2026, 4:19 p.m. |
Created at: March 20, 2026, 1:40 p.m.