Triple
T23195784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Jews |
E579865
|
entity |
| Predicate | globalEngagement |
P107585
|
FINISHED |
| Object | active in global Jewish causes |
—
|
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: active in global Jewish causes | Statement: [British Jews, globalEngagement, active in global Jewish causes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalEngagement Context triple: [British Jews, globalEngagement, active in global Jewish causes]
-
A.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
B.
engagementDomain
chosen
Indicates that an engagement, interaction, or activity occurs within or is associated with a particular domain, field, or area of focus.
-
C.
includesEngagement
Indicates that one entity incorporates or involves another entity in an engagement, interaction, or participatory activity.
-
D.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
E.
notableEngagement
Indicates a significant interaction, involvement, or participation between entities that is noteworthy or distinguished in some context.
- 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.