Triple
T23281305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COINTELPRO |
E588869
|
entity |
| Predicate | disclosureEvent |
P5035
|
FINISHED |
| Object | 1971 FBI office burglary in Media, Pennsylvania |
—
|
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: 1971 FBI office burglary in Media, Pennsylvania | Statement: [COINTELPRO, disclosureEvent, 1971 FBI office burglary in Media, Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disclosureEvent Context triple: [COINTELPRO, disclosureEvent, 1971 FBI office burglary in Media, Pennsylvania]
-
A.
discloses
chosen
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
B.
typeOfDisclosure
Indicates the specific category or nature of a disclosure made in a given context (e.g., legal, financial, personal).
-
C.
discoveryEvent
Indicates an event in which something previously unknown or unrecognized is found, identified, or revealed.
-
D.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
-
E.
claimedRevelationBy
Indicates that one entity asserts having received a revelation (e.g., divine, prophetic, or supernatural message) from another entity.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19643b8908190a2c29552b272dc61 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:57 p.m.