Triple
T8460152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kovno, Russian Empire |
E200019
|
entity |
| Predicate | hadSignificantCommunity |
P2321
|
FINISHED |
| Object | Jewish population |
—
|
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: Jewish population | Statement: [Kovno, Russian Empire, hadSignificantCommunity, Jewish population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSignificantCommunity Context triple: [Kovno, Russian Empire, hadSignificantCommunity, Jewish population]
-
A.
hasMajorCommunity
chosen
Indicates that an entity possesses a primary or significantly large community associated with it.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasCommunityLife
Indicates that an entity possesses or supports an active, ongoing pattern of social interaction, shared activities, and communal engagement among its members.
-
D.
hasCommunityServed
Indicates that an entity provides services or benefits to, or is intended to support, a particular community or group of people.
-
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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49fca788190a8728ff74f4d26f5 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.