Triple
T20473580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Café |
E502255
|
entity |
| Predicate | publiclyLeaked |
P86580
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Project Café, publiclyLeaked, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyLeaked Context triple: [Project Café, publiclyLeaked, 2011]
-
A.
leakedFrom
chosen
Indicates that information, material, or content has been disclosed or escaped from a particular source, typically without authorization.
-
B.
specificationLeakedIn
Indicates that the details or specifications of something have been disclosed or exposed within a particular context, location, or medium without proper authorization.
-
C.
abusePubliclyExposed
Indicates that one entity mistreats, exploits, or harms another entity whose sensitive information or vulnerabilities have been made publicly accessible.
-
D.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
E.
secretRevealedThrough
Indicates that a secret becomes known or disclosed by means of a specified channel, method, or intermediary.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e699639eec81908f8bd24877b2b876 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.