Triple
T5263050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mossad |
E118870
|
entity |
| Predicate | publiclyDiscloses |
P5035
|
FINISHED |
| Object | very limited organizational details |
—
|
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: very limited organizational details | Statement: [Mossad, publiclyDiscloses, very limited organizational details]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyDiscloses Context triple: [Mossad, publiclyDiscloses, very limited organizational details]
-
A.
discloses
chosen
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
B.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
C.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
-
D.
madePublicConfessionAt
Indicates that an entity openly admitted or confessed something in a public setting at a specific time or place.
-
E.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd2eff4819087420e30c140e6f6 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.