Triple
T35858615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish community of Hebron |
E1036577
|
entity |
| Predicate | wasExpelledIn |
P108675
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [Jewish community of Hebron, wasExpelledIn, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasExpelledIn Context triple: [Jewish community of Hebron, wasExpelledIn, 1929]
-
A.
expelledFrom
Indicates that an entity has been formally forced to leave or is removed from a place, organization, or institution, typically as a punishment or disciplinary action.
-
B.
expelledTo
Indicates that an entity has been formally forced to leave one place, organization, or group and sent to another specified location.
-
C.
requiredExpulsionOf
Indicates that one entity mandates or necessitates the expulsion or removal of another entity.
-
D.
expulsionReason
Indicates the cause or justification for which an entity was expelled from a group, place, or institution.
-
E.
expulsionEvent
chosen
Indicates an event in which an entity is formally forced to leave or is removed from a place, group, or institution.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.