Triple
T23195785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Jews |
E579865
|
entity |
| Predicate | issueOfConcern |
P150527
|
FINISHED |
| Object | antisemitism in the United Kingdom |
—
|
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: antisemitism in the United Kingdom | Statement: [British Jews, issueOfConcern, antisemitism in the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issueOfConcern Context triple: [British Jews, issueOfConcern, antisemitism in the United Kingdom]
-
A.
subjectOfConcernFor
chosen
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
-
B.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
C.
concernsProblem
Indicates that something is about, related to, or deals with a particular problem or issue.
-
D.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
E.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fdb279c81908dcc46f2786a86cd |
completed | April 29, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:06 p.m.