Triple
T10574189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mivtza Moshe |
E249567
|
entity |
| Predicate | causeOfTermination |
P41278
|
FINISHED |
| Object | public disclosure of the operation |
—
|
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: public disclosure of the operation | Statement: [Mivtza Moshe, causeOfTermination, public disclosure of the operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfTermination Context triple: [Mivtza Moshe, causeOfTermination, public disclosure of the operation]
-
A.
natureOfTermination
Indicates the manner, cause, or conditions under which a relationship, contract, or employment is brought to an end.
-
B.
reasonForDismissal
chosen
Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
-
C.
recommendedTerminationOf
Indicates that one party has advised or proposed that another party’s role, contract, or activity should be ended.
-
D.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
E.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52749dda08190b0c9627a931c5848 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.