Triple
T2552469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation London Bridge |
E56656
|
entity |
| Predicate | leaked |
P21842
|
FINISHED |
| Object | partially leaked to the press before 2022 |
—
|
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: partially leaked to the press before 2022 | Statement: [Operation London Bridge, leaked, partially leaked to the press before 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaked Context triple: [Operation London Bridge, leaked, partially leaked to the press before 2022]
-
A.
specificationLeakedIn
chosen
Indicates that the details or specifications of something have been disclosed or exposed within a particular context, location, or medium without proper authorization.
-
B.
exposed
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
C.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
D.
leakDate
Indicates the date on which something (such as information, content, or a product) became publicly known or was unofficially released.
-
E.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.