Triple
T17425123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish communities in the Papal States |
E423719
|
entity |
| Predicate | segregatedIn |
P127401
|
FINISHED |
| Object | ghettos |
—
|
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: ghettos | Statement: [Jewish communities in the Papal States, segregatedIn, ghettos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segregatedIn Context triple: [Jewish communities in the Papal States, segregatedIn, ghettos]
-
A.
segregatedFor
Indicates that one entity is separated or set apart from others specifically for the use, benefit, or association of another entity.
-
B.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
C.
segregatedRepresentation
Indicates that the representation of entities is separated into distinct groups or categories, rather than being combined or integrated.
-
D.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
-
E.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
- F. None of above. chosen
Provenance (4 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448fbfda88190be1c001d64289bf7 |
completed | April 19, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.