Triple
T31560044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weisz |
E805236
|
entity |
| Predicate | isOftenOfEthnicOrigin |
P120284
|
FINISHED |
| Object | Ashkenazi Jewish |
—
|
NE NERFINISHED |
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: Ashkenazi Jewish | Statement: [Weisz, isOftenOfEthnicOrigin, Ashkenazi Jewish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenOfEthnicOrigin Context triple: [Weisz, isOftenOfEthnicOrigin, Ashkenazi Jewish]
-
A.
mayBelongToEthnicGroup
chosen
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
B.
hasMajorEthnicMinority
Indicates that an entity includes a significant ethnic minority group within its overall population or composition.
-
C.
hasEthnicOrRegionalOrigin
Indicates that an entity originates from, or is associated with, a particular ethnic group or geographic region.
-
D.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
E.
isUsedByEthnicGroup
Indicates that something (such as an object, practice, or resource) is utilized or employed by a particular ethnic group.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:14 p.m.