Triple
T5016049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | App Store Small Business Program |
E112742
|
entity |
| Predicate | launchAnnouncementDate |
P429
|
FINISHED |
| Object | 2020-11-18 |
—
|
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: 2020-11-18 | Statement: [App Store Small Business Program, launchAnnouncementDate, 2020-11-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchAnnouncementDate Context triple: [App Store Small Business Program, launchAnnouncementDate, 2020-11-18]
-
A.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
B.
announcementDate
chosen
Indicates the date on which an announcement is formally made or becomes publicly known.
-
C.
announcedAt
Indicates that an announcement or declaration was made at a specific time or event.
-
D.
launchDateNote
Indicates a note or qualifier providing additional information or context about an entity’s launch date.
-
E.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732f4c5c8190b90f8e4daab458ee |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.