Triple
T34069233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Moshe |
E873717
|
entity |
| Predicate | relatedReligiousGroup |
P102165
|
FINISHED |
| Object | Jewish people |
E607
|
NE 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: Jewish people | Statement: [Operation Moshe, relatedReligiousGroup, Jewish people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedReligiousGroup Context triple: [Operation Moshe, relatedReligiousGroup, Jewish people]
-
A.
associatedReligionText
Indicates that there is a textual work (such as a scripture or religious document) that is specifically associated with, or pertains to, a given religion.
-
B.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
-
C.
religiousBranchOf
Indicates that one religion, denomination, or sect is a subdivision or offshoot of a larger parent religious tradition.
-
D.
religiousGroupMentioned
Indicates that a religious group is referenced or mentioned in the given context or statement.
-
E.
associatedReligionOrBelief
chosen
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
- F. None of above.
Provenance (4 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36ae4d79ac81909f9f39bf8e8385ba |
completed | June 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.