Triple
T28264002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google+ |
E712652
|
entity |
| Predicate | securityIncidentDisclosureDate |
P27009
|
FINISHED |
| Object | 2018-10 |
—
|
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: 2018-10 | Statement: [Google+, securityIncidentDisclosureDate, 2018-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityIncidentDisclosureDate Context triple: [Google+, securityIncidentDisclosureDate, 2018-10]
-
A.
dateOfExfiltration
Indicates the specific date on which data or information was illicitly removed or extracted from its original location.
-
B.
allegedInvolvementDate
Indicates the date on which an entity is claimed or reported to have been involved in a particular event or activity, without asserting that the involvement is confirmed.
-
C.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
-
D.
leakDate
chosen
Indicates the date on which something (such as information, content, or a product) became publicly known or was unofficially released.
-
E.
attackDate
Indicates the calendar date on which an attack or assault event took place.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 11:13 p.m.