Triple
T15548276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berdichev |
E370669
|
entity |
| Predicate | wasMajorJewishCenterInCentury |
P79379
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Berdichev, wasMajorJewishCenterInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorJewishCenterInCentury Context triple: [Berdichev, wasMajorJewishCenterInCentury, 19th century]
-
A.
wasMajorCenterDuring
chosen
Indicates that a place served as a primary or highly significant hub of activity, influence, or importance during a specified time period.
-
B.
wasMajorMiningTownInCentury
Indicates that a town was a significant center of mining activity during a specified century.
-
C.
centuryOfMajorMigration
Indicates the century during which a major migration event involving the entity took place.
-
D.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
-
E.
surveyedInCentury
Indicates that an entity was surveyed or systematically examined during a specified century.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a93121881909d88ca55a39252ac |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:08 a.m.