Triple
T31932277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salzburg witch trials |
E815285
|
entity |
| Predicate | hasVictimDemographic |
P142550
|
FINISHED |
| Object | women |
—
|
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: women | Statement: [Salzburg witch trials, hasVictimDemographic, women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVictimDemographic Context triple: [Salzburg witch trials, hasVictimDemographic, women]
-
A.
hasDemographic
Indicates that an entity is associated with or characterized by a particular demographic group or attribute.
-
B.
hasTypeOfVictims
chosen
Indicates that an entity is associated with victims of a specified type or category.
-
C.
hasDemographicPattern
Indicates that there is a characteristic distribution or trend of attributes (such as age, gender, income, or ethnicity) within a population or group.
-
D.
hasTypicalVictimRole
Indicates that an entity typically occupies the role of a victim in the context of a particular action, event, or relationship.
-
E.
hasVictims
Indicates that an entity has one or more individuals who have been harmed, injured, or adversely affected by it.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 12:04 a.m.