Triple
T5263007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mossad |
E118870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Israeli organization |
C14184
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Israeli organization Context triple: [Mossad, instanceOf, Israeli organization]
-
A.
Israeli government agency
chosen
An Israeli government agency is an official public body established by the State of Israel to implement laws, deliver public services, and administer specific governmental functions under the authority of the Israeli government.
-
B.
Zionist organization
A Zionist organization is a group dedicated to supporting, promoting, or advancing the political, cultural, or social goals associated with Zionism, particularly the establishment, security, and development of a Jewish homeland in Israel.
-
C.
Israeli company
An Israeli company is a business entity established and operating under the laws of Israel, typically headquartered or significantly active within the Israeli economy and subject to its regulatory, tax, and corporate governance frameworks.
-
D.
Israel–Jordan institution
An Israel–Jordan institution is an organization, body, or framework jointly established or formally recognized by both Israel and Jordan to manage, coordinate, or promote cooperation in areas such as security, water resources, trade, or diplomacy.
-
E.
Soviet organization
A Soviet organization is an institution, agency, or collective entity established under the governance and ideological framework of the Soviet Union to manage political, economic, social, or military functions.
- F. None of above.
Provenance (1 batch)
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. |
Created at: March 20, 2026, 1:51 p.m.