Triple
T36001469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraqi denaturalization law of 1950 |
E1041142
|
entity |
| Predicate | primaryAffectedGroup |
P207128
|
FINISHED |
| Object | Baghdad Jewish community |
E83086
|
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: Baghdad Jewish community | Statement: [Iraqi denaturalization law of 1950, primaryAffectedGroup, Baghdad Jewish community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAffectedGroup Context triple: [Iraqi denaturalization law of 1950, primaryAffectedGroup, Baghdad Jewish community]
-
A.
primaryGroup
Indicates that one entity serves as the main or most important group to which another entity primarily belongs or is associated.
-
B.
primaryClientGroup
Indicates the main group of clients that an entity primarily serves or is chiefly associated with.
-
C.
primaryUserGroup
Indicates the main or default user group to which a user is primarily assigned or associated.
-
D.
frontAffected
Indicates that an action, event, or condition primarily impacts the front side or front-facing part of an entity.
-
E.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
- F. None of above. chosen
Provenance (5 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38bff1e6fc8190adc304a8731c5dc1 |
completed | June 22, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.