Triple
T7770447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubrovno |
E179054
|
entity |
| Predicate | hasSignificantCommunityInPeriod |
P2321
|
FINISHED |
| Object | 19th century Jewish community |
—
|
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 Jewish community | Statement: [Dubrovno, hasSignificantCommunityInPeriod, 19th century Jewish community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantCommunityInPeriod Context triple: [Dubrovno, hasSignificantCommunityInPeriod, 19th century Jewish community]
-
A.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
hasMajorCommunity
chosen
Indicates that an entity possesses a primary or significantly large community associated with it.
-
C.
hasHistoricCommunity
Indicates that an entity is associated with, contains, or is part of a community of historical significance.
-
D.
hasCommunityAspect
Indicates that something involves, reflects, or contributes to a shared community dimension, such as collective participation, interaction, or benefit.
-
E.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c70438ca2481909114b0c434717109 |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:11 p.m.